On Jun 8, 5:16 pm, Oveek <[email protected]> wrote:
> That's really due to one of my assumptions about performance. If the
> text store gets very large with many tiddlers and revisions, I guess
> its performance becomes tied to how well the file system handles large
> numbers of small files. I think a database mitigates that aspect of a
> filesystem's role in performance. There are also some facilities like
> locking, and handling concurrency that could come in useful in a multi-
> user environment. If my planned test setup evolves into a more serious
> deployment with a wider user base and heavier load, I feel like a
> database backend is more suited to the task.
This is all probably true.
> Now I'm thinking I'll just
> setup the test as a free-for-all, sit back and see what comes up
> rather than instituting a whole bunch of controls that complicate
> policies and bag structure.
This seems like a great plan: Set things up, see how it goes, see
what's needed. Adding new stuff is easy enough that it's not likely to
slow you down too much if you discover you need to make some
adjustments.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"TiddlyWikiDev" 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/TiddlyWikiDev?hl=en
-~----------~----~----~----~------~----~------~--~---
