---console--session--excerpt--start----
SQLITE_NOMEM: failed to allocate 651456745 bytes of memory
SQLITE_NOMEM: statement aborts at 22: [INSERT INTO
blob(rcvid,size,uuid,content)VALUES(6,662828201,'9b81ec309fc0c2f2278f386c8b1917359fe24bd8',:data)]
fossil: SQL error: out of memory
SQLITE_ERROR: statement aborts at 1: [ROLLBACK] cannot rollback - no
transaction is active
---console--session--excerpt--end------
The obvious line of thought might be that
I should just upgrade my hardware, but if there's
no fundamental reason, why files can not be
committed in chunks, then it would be nice if
the Fossil just took a look, how much RAM
is available and then use some formula to
allocate some percentage less than 100% of the
free RAM and then try to do all of the work
within that RAM. May be the default minimum
might be 5MiB (five mebibytes), but the minimum
might also be an optional console parameter.
The idea is that some embedded systems have only
64MiB of RAM, which is actually pretty much,
given that in the 90'ties my desktop computer
had about 40MiB. (I'm born in 1981, so I was
a teenager in the 90'ties.) That 40MiB allowed me
to play Wolfestein and, I do not remember exactly,
but may be even Doom_2.
The old Raspberry Pi 1, which has a single 700MHz CPU-core,
has about 400MiB of RAM (512MIB minus video memory).
The new Raspberry Pi 3, which has 4 CPU-cores, has
about 900MiB of RAM (1GiB minus video memory).
Given the "Trusted Computing" trends of the Intel and AMD CPUs,
a solution, where a private cluster of Raspberry Pi like
computers is used in stead of a single, "huge", PC,
becomes more and more relevant. There are even academic
projects that try to construct such personal work stations
https://suif.stanford.edu/collective/
The industry has been contemplating about virtual machine
based separation for quite a while:
https://www.qubes-os.org/
Although, in my view the most elegant solution
for separating and then "re-joining" different applications
on a single machine is the
https://genode.org/
Historically speaking, may be one of the first, if not the first,
cluster based personal work station idea was in the
form of the Plan_9 operating system, which seemed to
be more of a cluster based single server with terminals
than a workstation, but the general idea seems to be there.
http://www.plan9.bell-labs.com/wiki/plan9/plan_9_wiki/
That is to say, a cluster of Raspberry Pi like computers
has a long history of trial and error and even, when the
cluster has a lot of RAM, that RAM is separated to relatively
small chunks between the Raspberry Pi like computers.
The ability to either parallelize the task or to
try to get by with a small amount of RAM can be practical.
Thank You for reading my comment :-)
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
