On Saturday, December 7, 2019 at 12:18:16 AM UTC-5, TonyM wrote: > > that would mean something is broken then? > > Not necessarily broken with TW. The Rpi 3 is limited to 1-2GB of RAM AFAIK and we don't know how much RAM the OP has. One question I have is, if the TW file is a zip file (my assumption), then on average, all the compression of the text (which includes user-entered content and source code) is about 70%. So a 1GB compressed file compressed at 70% (or is 30% of the original size) has an uncompressed size of 1GB/0.30 or 3.3GB, beyond the RAM capacity of the RPI3. So when the Raspbian OS runs out of RAM, it starts paging RAM to a file (possibly on a micro SD card) frantically, and that's why it takes so long.
Also, how big is each tiddler and how many images are in the TW file, and how big are the image files? Those are all variables I'd like to know about. Also the Rpi 3 is a low end CPU and it's not that fast. So I'd like to know: 1. How much RAM does the RPi3 have? 2. Is the OS on a micro SD card, USB hard drive, or something else? 3. How big is the TW html file (which is the compressed size)? Another question is, when TW is opened (and it sounds like the OP is using the node.js version of TW), how often is the disk accessed? Since Rpi could be running off a micro-sd card, or USB hard drive. Throughput of USB is not that great and has never, IME, reached theoretical speeds. USB throughput IME has only reached 10% of theoretical speeds on average, and not much more than that. -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/f7b1fc7c-68bf-4db5-8cfb-5de854b3e78d%40googlegroups.com.
