virtualizing any given function call is highly context
dependent.
Sincerely,
--
Jonathan Brandmeyer
[0]: https://valgrind.org/docs/manual/cg-manual.html#branch-sim
[1]:
https://www.valgrind.org/docs/manual/cl-manual.html#cl-manual.options.simulation
[2]: https://valgrind.org/docs/ma
On Mon, Oct 21, 2019 at 5:47 PM Richard Hipp wrote:
>
> On 10/21/19, Jonathan Brandmeyer wrote:
> >
> > No significant change. The target filesystem only caches non-aligned
> > writes, so there usually isn't anything for it to do on fsync anyway.
> >
>
>
4kB pages, but it is a particularly unfavorable row size for 2 kB
database pages.
--
Jonathan Brandmeyer
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
On Mon, Oct 21, 2019 at 5:00 PM Richard Hipp wrote:
>
> On 10/21/19, Jonathan Brandmeyer wrote:
> > On Mon, Oct 21, 2019 at 10:31 AM Richard Hipp wrote:
> >>
> >> On 10/21/19, Jonathan Brandmeyer wrote:
> >> > Or, how many times is each page written
On Mon, Oct 21, 2019 at 10:31 AM Richard Hipp wrote:
>
> On 10/21/19, Jonathan Brandmeyer wrote:
> > Or, how many times is each page written by SQLite for an insert-heavy
> > test? The answer appears to be "4", but I can only account for two of
> > those fou
ill seems too high.
Any other ideas?
Thanks,
--
Jonathan Brandmeyer
___
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
--
Jonathan Brandmeyer
Vice President of Software Engineering
PlanetiQ
_
On Wed, Jun 12, 2019 at 12:02 PM David Raymond
wrote:
> https://www.sqlite.org/fileformat2.html#record_format
>
> The storage type of each record is given by an integer. And in the current
> format, all non-negative integers are used.
>
Ouch. Yes, an additional data type was closer to what I ha
; ___
> sqlite-users mailing list
> sqlite-users@mailinglists.sqlite.org
> http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
>
--
Jonathan Brandmeyer
Vice President of Software Engineering
PlanetiQ
ly` would have
Just Worked, `git rebase master` from a patch series would have Just
Worked, and a merge-based workflow would have Just Worked, too.
--
Jonathan Brandmeyer
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
r mistake onto the
corrected master. User's would need to perform a one-time `git rebase
--onto master mistake ` instead.
--
Jonathan Brandmeyer
___
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
On Wed, Apr 3, 2019 at 8:55 AM Richard Hipp wrote:
>
> On 4/3/19, Jonathan Brandmeyer wrote:
> > What is the upper bound for stack consumption under the
> > SQLITE_USE_ALLOCA compile-time option? I see that there are a number
> > of configurable size limits available as
What is the upper bound for stack consumption under the
SQLITE_USE_ALLOCA compile-time option? I see that there are a number
of configurable size limits available as compile-time and/or run-time
options. Which ones affect the maximum alloca?
Thanks,
Jonathan Brandmeyer
13 matches
Mail list logo
