I expect my site to sustain something around 1000-3000 new user
acquisitions per day, all of which will account for an insert
into 3
GIST indices.
Most people when they talk about a large load on a DBMS system
talk about transactins per second. As in 100 per second
Even if we only
Oleg,
Daniel and I have both been collaborating on this structure for a while now.
We are aware that GiST reads work very fast. But won't they be paralyzed
when there are writes? Both of us are working on dating sites, and the main
problem that concerns us is a very heavy traffic load. At this
Patrick,
you didn't say us about your setup. Have you proved you've seen
locking issue for reading ? Are you sure you have no any locks in
your code ? Any tests demonstrated your problem would be great.
Oleg
On Tue, 9 Nov 2004, Patrick Clery wrote:
Oleg,
Daniel and I have both been
Daniel,
concurrency is a big issue of current implementation of GiST.
But it should don't bite you for READ ops !
-hackers mailing list is a very relevant mailing list for GiST
discussions. It's pity we several times claimed to work on GiST
concurrency and recovery, but never got a chance :)
I
