Re: Price Editor/Database lag

PS: Sometimes, trees of trees/containers outperform having everything in one tree/container. If the quotes for each symbol are in a separate container, the RAM hit to query or churn data for that symbol is minimized. If the data is kept sorted in all storage forms (when inserted into the

Re: Price Editor/Database lag

I discovered my vm.swappiness=60, dropped it to 10 as recommended for desktop LINUX. Now no si/so on vmstat, but a peak in cs and a moderate delay, around 20 seconds, when adding price quotes. Again, it looks like it is using too big a RAM space to manage this data, or some similar process

Re: Price Editor/Database lag

I started vmstat -tw 11 in a wide xterm and I do see a lot of swap out for some but not all delays. The not-first delays seem to be smaller now. The first delay did 3K+ so, later ones did 2K+, 300+ or almost no so. Almost no so may indicate the container is not dealing well with the volume and

Re: Price Editor/Database lag

; Sent: Mon, Apr 2, 2018 11:30 am Subject: Re: Price Editor/Database lag I just discovered my swap was all turned off. It might also explain very un-VM messages like "Your computer does not have enough free memory to automatically analyze the problem and send a report to the develope

Re: Price Editor/Database lag

gnucash-user <gnucash-user@gnucash.org> Sent: Sun, Apr 1, 2018 11:09 pm Subject: Re: Price Editor/Database lag Entirely possible. I’m not too familiar with the GtkTreeList implementation. Regards, John Ralls On Apr 1, 2018, at 6:59 PM, David <dgpick...@aol.com> wrote: J

Re: Price Editor/Database lag

; > > David > > > > > > -Original Message- > > From: John Ralls <jra...@ceridwen.us <mailto:jra...@ceridwen.us>> > > To: David <dgpick...@aol.com <mailto:dgpick...@aol.com>> > > Cc: Gnucash Users <gnucash-user@gnucash.org >

Re: Price Editor/Database lag

- > > From: John Ralls <jra...@ceridwen.us> > > To: David <dgpick...@aol.com> > > Cc: Gnucash Users <gnucash-user@gnucash.org> > > Sent: Sun, Apr 1, 2018 3:48 pm > > Subject: Re: Price Editor/Database lag > > > > Please remember to copy the

Re: Price Editor/Database lag

t; > > -Original Message- > From: John Ralls <jra...@ceridwen.us> > To: David <dgpick...@aol.com> > Cc: Gnucash Users <gnucash-user@gnucash.org> > Sent: Sun, Apr 1, 2018 3:48 pm > Subject: Re: Price Editor/Database lag > > Please remember to c

Re: Price Editor/Database lag

and price.) Maybe it is going into thrashing? Thanks, David -Original Message- From: John Ralls <jra...@ceridwen.us> To: David <dgpick...@aol.com> Cc: Gnucash Users <gnucash-user@gnucash.org> Sent: Sun, Apr 1, 2018 3:48 pm Subject: Re: Price Editor/Database la

Re: Price Editor/Database lag

cache of > public data, and can be shared with all if they use the same key symbols, > updated once for all sets of books! > > > > -Original Message- > From: John Ralls <jra...@ceridwen.us> > To: DGPickett <dgpick...@aol.com> > Cc: gnucash-user <g

Re: Price Editor/Database lag

> On Apr 1, 2018, at 5:51 AM, DGPickett via gnucash-user > wrote: > > Since I was collecting prices daily, I guess my price database is pretty > large, and my family finances are in there for about 5 years. I have xml > database, and compressed, but I checked my

Re: Price Editor/Database lag

Since I was collecting prices daily, I guess my price database is pretty large, and my family finances are in there for about 5 years. I have xml database, and compressed, but I checked my save intervals, even increased them, but no help. My PC has 8 GB ram, and a very large solid state swap

Re: Price Editor/Database lag

You don't necessarily have to update manually. The original Yahoo source has been ruined, but you can (and I do) use "yahoo_json" as a source. It's worked fine for me. As for your actual question, I'm sorry but I've no idea. I'm running on Mac OSX. People might have some inquiries about the

Price Editor/Database lag

Now that I am manually updating my stocks monthly, thanks, Yahoo, I find that as I pull up the price history to clone a new month end entry for the symbol, I get a _*long (30 second) gray out delay*_ (on Linux, and not the newest PC) at some point in the cycle, like a premature auto save or