On Jan 22, 4:38 pm, "[email protected]" <[email protected]> wrote:
> > After having readhttp://www.tiddlywiki.org/wiki/Performance_IssuesI > realize that several MB are already a lot for TiddlyWiki and > converting my current content would result in a huge unusable thing. > Managing a lot of content efficiently probably really takes some > server software that can do preprocessing and caching and ideally > includes a full fledged database. Right now I think I will have to > leave my current content on my private machine at home. At work I'll > start with a blank TiddlyWiki and hope I'll get by with it for a > while, before it grows to large. Hopefully I have a better idea by > then 8-) > Hi Timon, I too have confronted the same issue and I don't know how Eric at TiddlyTools.com does it- dense and rich but still loads quick! Nevertheless here are some observations of my experiments on scale: I've successfully tested TiddlyWiki for a knowledge base I help coordinate and found that I had to offload the assets to the filesytem and use TW more as a frontend viewer than a single all encompassing repository in order to contain the scale issue - So that large topics of styled content are contained in iframes on a shared or local drive as in tiddler body: <html> <iframe style="background-color:#ffffff; border-color:#ffffff; border:none;" width="640" height="480" frameborder="0" scrolling="yes" src="file://///pathtoyourfile" title="filename"></iframe></html> Images are handled in the same way: [img(480px,auto)[file:///path/to/your/image]] It was under 3MB covering 1000's of topics and associated images along with an issue log. But nothing like 17MB! Judicious use of an archival method to further segregate old from new content also helps. I've used this effective combo: ToDoTogglePlugin with CheckboxPlugin along with the essentials from Eric's TiddlyTools: Import and Export Tiddlers Plugins to manage that archival process. Udo's YourSearch along with his other plugins are also excellent for culling. I also tried using a flat file system with the data and going csv with the DataListPlugin at the http://baggr.tiddlyspot.com/ which leverages Udo's DataTiddlerPlugin. It's great for long list lookups but ultimately stayed with the tiddler as unit KISS route as is much more familiar UI. Before that I did do a taste of running php5 locally then used BidiX's upload plugin http://tiddlywiki.bidix.info/#[[UploadPlugin%204.1]] for a flavor of local serverside, but abandoned once I got proof of concept. Finally, I've been experimenting with TiddlyWeb (AKA mother of all server sides) since it currently uses a local text store where tiddlers are file revisions in folders. You can make recipes from bags of tiddlers and mix and match rolling your own collection. The thing about TiddlyWeb is that my puny brainz doesn't have to know how to configure Apache or some other server magic, but sounds like you have the smart for that and serverside is not an issue for you. Chris Dent http://peermore.com/tiddlyweb/dist/ and FND works with TiddlyWeb. So there are options if you want to stay local, but as we've seen over the years, scale is an important question when working lots of stuff in TW. And it sounds like you've acumulated a lot of stuff, so a small army of TWs may be needed with a good workflow! :-) hth Best, tony --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
