On Thursday, February 13, 2020 at 8:08:07 AM UTC-8, PMario wrote: > > That shouldn't be the case. see info above. > > >> When I tried to make a TW with 37000 vocabulary entries, it slowed to a >> standstill because the tag operator apparently isn't optimized for large >> numbers of tagged tiddlers. It turned out to be faster to do a search in >> the tag list field, which is surprising. >> > > It would be interesting to know the filter strings you used and how the > tiddler / tag structure looked like. > Latest TWs have a $tw.perf.log() function, which can give detailed info, > in the dev-tools if performance-instrumentation is enabled. ... > > -mario >
It wasn't something convoluted, if that's what you're getting at. It was a simple tag[xxx] functionality that slowed to a crawl when there were thousands of tiddlers tagged. Replacing the tag operator with a search operator improved performance. There's no real hierarchy -- just a handful of tags to indicate that a tiddler is word, and what kind of functionality it has (adverb, verb, etc.) It was surprising that the tag operator performed so poorly. It's not something that I want to recreate. I now have 72000 entries, and get reasonable performance on a tablet -- but I don't use the tag operator. -- 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/0c047c84-2c52-474a-9d17-4de28e345d07%40googlegroups.com.
