On Tuesday, August 1, 2017 at 1:18:37 AM UTC-4, John Wiegley wrote: > > > I would expect ledger to handle millions of transaction gracefully, so I'm > interested in your example that times out. > > -- > John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F > http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2 >
Hi John. The file I generated using the script posted earlier may be found here <https://www.dropbox.com/s/s5ajf2e13t0ribu/benchmark.ledger.xz?dl=0>. I grabbed a couple of other systems and tried a bal command on the file, with the same results for all: Killed after a short time. Running dmesg | grep -E -i -B10 'killed process' shows: [ 3836.170988] Out of memory: Kill process 15328 (ledger) score 644 or sacrifice child [ 3836.170994] Killed process 15328 (ledger) total-vm:6667128kB, anon-rss:6570560kB, file-rss:0kB, shmem-rss:0kB Two of the three sample systems have 8GB of RAM (ledger v 3.1.2-20160801), the other has 4GB (ledger v 3.1.0-20141005) and none had anything other than the base desktop environment running at the time. Perhaps a quirk of the script at these large numbers is causing the issue. I'm not familiar enough with awk to determine that on my own, however. -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
