Re: Global data concurrent access ?

Michael Petrotta <mpetrotta@xxxxxxxxx> wrote:
Out of interest, what happens to the figures if:

1) You're on the same box?

No pooling 1000 iterations. Elapsed time: 00:00:06.0936720
Pooling 1000 iterations. Elapsed time: 00:00:00.2499968

2) You're only one network hop away?

No pooling 1000 iterations. Elapsed time: 00:00:12.7683600
Pooling 1000 iterations. Elapsed time: 00:00:00.2904176

Interesting. The results are repeatable, but it's not a perfect test
(in particular, the client for #2 is a much slower laptop).

Wow. Just shows how wrong intuition can be!

If I take the results at face value, it seems to say that network speed
affects pooled connections (makes sense; there's not much connection
setup and teardown with pooled connections. It's just the time taken
to get the query and results over the wires).

Yup.

I think the speed of my laptop is affecting the non-pooled test; it's
taking time to have ADO.NET set up and tear down the connection.
Unfortunately, our network architecture is such that it's hard to have
two powerful desktops closely connected.

Fair enough - thanks for taking the time to run the tests at all!

(The speed of pooled connections in general surprised me, when I first
ran this test. I'd assumed network latency would give me round-trip
times around 10-20ms. Pings to the server are also returning
sub-millisecond times. Remember modems and their 200ms pings?)

It's quite incredible how fast some things can change while others stay
the same. Where are the 1TB+ cheap, fast static memory chips that we've
been waiting for for so long? That's what I think will *really*
transform computing...

--
Jon Skeet - <skeet@xxxxxxxxx>
http://www.pobox.com/~skeet Blog: http://www.msmvps.com/jon.skeet
If replying to the group, please do not mail me too
.

Relevant Pages

  • Re: Global data concurrent access ?
    ... No pooling 1000 iterations. ... Elapsed time: 00:00:12.9217096 ... That's about 12ms per round-trip for a non-pooled connection, ...
    (microsoft.public.dotnet.framework)
  • Re: Global data concurrent access ?
    ... No pooling 1000 iterations. ... Elapsed time: 00:00:12.9217096 ... affects pooled connections (makes sense; ...
    (microsoft.public.dotnet.framework)
  • Re: Strange behaviour with Xilkernel
    ... context switches occurs continuously. ... Now, each M iterations, I ... with the real elapsed time. ... the real elapsed times. ...
    (comp.arch.fpga)
  • Re: Global data concurrent access ?
    ... No pooling 1000 iterations. ... SqlConnection(String.Format(connStringPooling, server, database))) ...
    (microsoft.public.dotnet.framework)
  • Re: Denesting
    ... 10000000 iterations of WORK0 take Elapsed time: 00:00:01.015 ... 10000000 iterations of WORK1 take Elapsed time: 00:00:01.297 ... 10000000 iterations of WORK2 take Elapsed time: 00:00:02.890 ...
    (comp.lang.forth)
Loading