Re: [Exist-development] [Exist-open] Performance of concurrent read queries.

[Jason S. <js...@in...>]

The reason I have been sort of a pain in the tuckus about this is not to get a quick fix, but to get this on the roadmap. :-) I definitely don't want to lose it.



-----Original Message-----
From: Adam Retter [mailto:ad...@ex...] 
Sent: Tuesday, August 31, 2010 6:47 AM
To: Jason Smith
Cc: Wolfgang Meier; Paul Ryan; eXist development; Michael J. Pelikan; Todd Gochenour
Subject: Re: [Exist-development] [Exist-open] Performance of concurrent read queries.

> Again, I would not expect a final solution to be implemented the way I have done it.  I just want to be able to show some possibilities.

I am really excited to see such enthusiasm and knowledge of the
eXist-db internals and suggestions for improvements that could be
made.

> I am not expecting this conversation to take place quickly.  This is one of those "long-haul" things - perhaps over years, and several major releases.  I'm not in a hurry to do the wrong thing quickly!!!
>

Lets not loose this though, I think that any performance and
scalability enhancements are great.

And actually there is a flip side here that no one has mentioned:
Whilst everyone has said that you should have optimised queries and
appropriate indexes, which is invariably true for production systems,
what about new users and developers who come to eXist-db?
As a new user of eXist-db you dont necessarily understand about
optimising your queries or even how to create the correct indexes. Not
all eXist-db users are software developers! It would be great if these
new users saw great performance from the start, even if they havent
set up indexes and their queries are doing full scans of the dbx files
:-)