Re^3: Musings about a database ecology

Perhaps it's just a function of the vagueness required by whatever job you happened to be in, but everything you say sounds like a severe case of premature optimization. You *sound* like you have no idea what is slowing down the system so you'll just implement some kind of locking system to hopefully make it go faster?! But maybe you do have a very good idea of what is going wrong, and you just can't tell us, but in this case, how are we supposed to help you?

From here I just see "Well I've got this system, and it works fine with 100 documents but it sucks with 6000 documents, so I'm going to do X", but I, at least, have no idea if X will help or not because you've told me nothing about the system.

Or possibly I'm just confused because I don't understand enough of what you've said about what the system actually is or does.

Comment on Re^3: Musings about a database ecology

Replies are listed 'Best First'.
Re^4: Musings about a database ecology by talexb (Chancellor) on Dec 20, 2004 at 20:21 UTC
Fair enough .. thanks for your input. I know I've been vague, partly because of NDA rules but partly to try and conceptualize the environment. I think I may try Devel::Profile on the task that says "Hey!" and see what results I get. Alex / talexb / Toronto "Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds	[reply]
Re^5: Musings about a database ecology by BUU (Prior) on Dec 20, 2004 at 20:45 UTC
Sounds like a very good idea =]	[reply]