I have a single-file TiddlyWiki that uses tm-http-requestto submit a query to a remote database server containing Canadian “address” data. The server returns a block of JSON text, which is then expanded into separate tiddlers using a custom $action-unpackdata widget that recursively “walks” the JSON object structure and outputs a tiddler for each field of each object in the JSON. Depending upon the query criteria, this results in somewhere between several hundred and about 30,000 $:/temp tiddlers… for which the “in-use” lag is barely noticeable.
However, the “worst case” usage (with no specific query criteria) returns the entire database contents as a very large block of JSON text (about 27Mb). When unpacked, this creates almost 680,000 $:/temp tiddlers!
As you would expect, this seriously affects the responsiveness of the entire TiddlyWiki interface (I even get some brower-based “do you want to wait?” messages during the “unpack” processing). Nonetheless, it does NOT crash the TiddlyWiki, and as soon as I delete those $:/temp tiddlers (which triggers some more “do you want to wait?” messages), the responsiveness returns to normal.
Note that because these are $:/temp tiddlers, they are NEVER saved in the TiddlyWiki file, so the in-use lag is only a transient effect that does not affect the load time in any way.
-e