h03p, Sounds like this is a case where TiddlyWiki's success means your demand on it increased. As they say, "our needs expand to fill the resources available".
- You are aware of performance improvements with indexing in the 5.1.20 pre-release? - You can move content to skinny tiddlers and external media files canonicalURL - You can use html object tags to include external content at "run time" - You can use node to access static versions of tiddlers, without loading the wiki. - Are you aware of Jeremys Amazon Web Services deployment of a large tiddlywiki? - There are plenty of ways to integrate independant wikis so it is always possible to divide and conquer - You could also insert subroutines that are processed elsewhere with some cunning design. - Custom indexing, compression another tricks could be used in extreme circumstances. I use tiddlywiki a lot, it is one of my main applications suits, mostly self build wikis. This means I load a lot more in my browsers than most. I have a 16GB Ram laptop. As a result* I lifted the maximum ram available to Chrome and FireFox* (in their settings) so they can use a greater share of my laptops ram and they perform even better as a result. If we move from executables to browsers we should give browsers the resources they need. People forget this because they are so often working to reduce the wikis use of browser resources they forget they can give the browser more resources. Sometimes the best method is loosely coupled TiddlyWikis. I can drag and drop tiddlers and tiddler bundles between wikis using an iframe and the multi-user and multi-access methods that continue to be developed will only make this easier. Some more responses. There's only so much optimization TW5 and the browsers which run it can > achieve. We're hitting the limits of single-threaded performance, and I am > not convinced there are many huge gains left for javascript in the browser > on high-end x86_64 CPUs (I desperately hope I'm wrong). Performance for > large TWs is looking a bit grim. I'm trying to look down the road 10 years > from now and ask myself if my Tiddlywiki is going to be the right tool for > the job. It's an amazing rapid-prototyping tool, but maybe it can't be made > performant enough. What do you think? > I do not think we need more threads I think it can adapt a great deal, not to mention new developments to respond to future issues. > > Even though I'm still a noob at it, I use TW a lot > <https://www.google.com/url?q=https%3A%2F%2Fphilosopher.life%2F&sa=D&sntz=1&usg=AFQjCNEIleHYKzZsWgvDsi7hbhcQ-iM2Iw>; > > I'm an addict. In 3 years, I've amassed 10k tiddlers of almost pure text in > a 30MB TW (that's ~60 novels in length), and I don't see myself slowing > down. I don't do anything fancy, but this tool is heavily integrated into > my life. I'm a unificationist too: part of the strength of this tool is > that I don't have to separate it into unconnected documents. I want to > search, navigate, hyperlink, and construct the whole. Unfortunately, the > tool is getting slower and slower for me. I'm pretty worried I need to move > away from Tiddlywiki. > Try my suggestions above if this persists, give us the opportunity to address it. I do not think you will need to move away, just tackle it differently. > The standout property of Tiddlywiki is that I get to serve a > self-modifying IDE+Product as a single html file (though I no longer > develop it without Bob). The client's browser does most of the calculation, > and I don't have to rely upon having a server which does anything more than > dishing out static files; I'm not beholden to centralized webservers > (though I still use github for now). I adore how it is censorship > resistant, cryptographically signable, easy to distribute, and it runs on > almost any device (though, at this point, my wiki barely runs on a phone). > It's perfect for P2P-serverlessness. There is nothing else like it in this > respect unless I'm handing someone a complete VM or container, but that > doesn't work nicely in a browser. There is no replacement as far as I can > tell. > I don't try and get my primary wiki working on mobile, I design independent solutions and integration as needed. > > I've probably made plenty of mistakes in attempting to optimize, but I'm > trying. I try to stick to hardlinks, and I do my best not to generate > anything dynamically when I can. There's only so much optimizing one can do > for complex filter expressions. I even bend over backward to do what I call > "Firmcoding" in which dynamically generated lists are pre-computed into > static indexes (basically, this enables link references to function, limits > clientside computation, and if I have to move out of Tiddlywiki, all of my > linking structures are still hardcoded). What kinds of precomputing can I > do here to help the client side? I've only started really using tags this > past year, and I just ripped out all of the tags to find almost no > performance gains either. Do I have too many tiddlers? Do I need to start > finding ways to molecularize (rather than atomize) content into larger > tiddler bodies and then build specialized parsing for those large tiddlers? > I'm growing desperate. > Do not get desperate until you have followed all leads. Recent discussions suggest in computation intensive tiddlers, you can take a snapshot (to a static Tiddler) and show that rather than the active tiddler) so no widget tree update will be necessary when other things change. In an application I am building, I am creating a mechanism to identify when such a refresh may be needed and indicate as such. > > I feel like I'm going to puke. I've seen this coming for a while, and I've > been burying my head in the sand hoping it wasn't true. This is my evolving > horcrux-pensieve, and now I feel like a hermit crab who might have to find > another shell. I'm heartbroken at the thought. This is the best damn tool I > have ever used in my entire life; I can't bear to lose it. NO! NO! > NOO!!!!!!!!! /hissy-fit. > I believe your anxiety is unwarranted. > > Is there no hope for me here? Will the next TW-X be built with WASM? What > other toolset do you recommend for me? Where should this pilgrim go, and > what should he do? > If TWX makes this simpler for you I do not know, but I seriously believe we have the technology to avoid what ever you may throw at it, just sometimes you may need to re-engineer things. TiddlyWiki is extensible in so many directions out of the box, and easy to modify and extend. Regards Tony -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tiddlywiki. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b53d6257-ac10-4346-88b2-5cdef544c461%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
