Magnus Hagander wrote:
IIRC, there hasn't been any direct benchmark for it (though I've wanted to do
that but had no time), but it's been the olnly real explanation put forward for
the behaviour we've seen. And it does make sense given the thread-centric view
of the windows mm.
/Magnus
How is it supposed to be slow, once its mapped into your process?
There's no OS interaction at all then.
If you are suggesting that the inter-process synch objects are slow,
then that may be so: just use interlocked
increment and a spin lock in place of a mutex and use an associated
event to wake up if necessary.
You dont have to use a named kernel mutex, though it may be handy while
setting up the shared memory.
If you are repeatedly changing the mappings - well, that may be
something that needs optimisation.
James
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
