I'm the guy with 60,000 plus tiddlers. That turned out to be an issue with tag optimization. I changed my filters to not use the tag operator, and now my TW app works reasonably well even on a Kindle Fire.
You might do a search on javascript abilities. A quick search suggested that javascript arrays could hold 4 billion entries. You will be out of browser memory long before that happens. I think it's hard to document the exact range of abilities of TW because there are so many platforms, hardware, OS, browser differences. To me the impressive thing is that we have someone in the forum who actually runs a store on TW ! Hardware memory seems to be a major consideration. A file may be only 10 megs, but the javascript it runs appears to need to spread out and take several times that amount of space. Or at least that's what I've observed. If I was seriously considering creating a mammoth app in TW, I think I would start by figuring out the basic relationships I would want between tiddlers (fields, tags). Create a few sets of tiddlers. Then run some process to clone thousands of test tiddlers. Then you would have a feel for how things were going to work. At this point, avoid using the tag operator in filters were there will be huge numbers of tiddlers tagged with that tag. But 5.1.19 isn't the TW version to be using. Optimizations were made in 5.1.20 that allow for larger TW files. So it's probably worth upgrading, unless there is something specific about 5.1.19 that you need. Good luck! On Monday, November 25, 2019 at 7:43:14 AM UTC-8, Chuck R. wrote: > > Thanks TiddlyTweeter, but what issues could I expect from the browser > side? On a 16-bit system there is a limit on how high an integer will go, > it will count up to a 16-bit value. On a 64-bit system there is a limit on > the value of unsigned integers, but it's really high, in the billions at > least. > > We've had some questions here that someone gets some type of error and > they have 60,000+ tiddlers in a single file. The max value for an unsigned > int is 65536. This is only relevant if TW5 uses unsigned integers to give a > unique number to each tiddler. What if it uses a base 36 or base 64 > numbering system? Or something else? > > So if I'm using the most recent version of Chrome, and it's a 64-bit > browser, what issues could I expect, if any, from the browser or OS end of > things? > > Does the version of Javascript used by TW5 have any limits? Has it been > updated to support 64-bit operating systems and 64-bit data types? > > Thanks. > > > > > -- 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 tiddlywiki+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/8a146866-f04b-4d1a-88c2-283ea538bc30%40googlegroups.com.
