No, I have not. The .timer discrepancy is due to the overhead of memory management which is done via DPC's and thus they accrue to the Supervisor and not the user process, the user process sees it as missing time. The underlying issue with the cache stride management has not been addressed yet ...
--- The fact that there's a Highway to Hell but only a Stairway to Heaven says a lot about anticipated traffic volume. >-----Original Message----- >From: sqlite-users [mailto:sqlite-users- >boun...@mailinglists.sqlite.org] On Behalf Of curmudgeon >Sent: Saturday, 22 September, 2018 08:17 >To: sqlite-users@mailinglists.sqlite.org >Subject: Re: [sqlite] .timer > >Keith, did you ever get any feedback from ms about this bug? There's >certainly been no windows update that solved the problem. > > > >-- >Sent from: http://sqlite.1065341.n5.nabble.com/ >_______________________________________________ >sqlite-users mailing list >sqlite-users@mailinglists.sqlite.org >http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
