Andrea Aime wrote:
> I was wondering, is that (grabbing the write lock while still
> possessing a read lock) supposed
> to be happening, or is it just a bug in how the lock calls are being
> made?
It was intensional; we need to actually read the shapefile in order to
make a copy of it (ie in o
Jody Garnett ha scritto:
> Nothing went wrong that I know of; my impression was Jesse stalled
> waiting for feedback. Do you want to try a read/write lock?
In fact I already tried with a crude patch, just to get an idea.
The main problem with using
http://java.sun.com/j2se/1.5.0/docs/api/java/ut
Nothing went wrong that I know of; my impression was Jesse stalled
waiting for feedback. Do you want to try a read/write lock?
Jody
Andrea Aime wrote:
> Hi,
> I'm looking into a scalability problem in our current
> shapefile datastore implementation that prevents
> fully using the whole CPU(s) on
Hi,
I'm looking into a scalability problem in our current
shapefile datastore implementation that prevents
fully using the whole CPU(s) once the number of threads
hitting the shapefile is > 1.
I only had a cursory look, so I may have misunderstood,
but it seems the current locking mechanism tells
