Chaosty wrote:
It runs on the same server, php memcached connects by 127.0.0.1 to it.
it close but not the same. i did kill and run clean memcached server,
each time it was close to 0.1 sec.
In that case, I totally agree this is suspicious.
Just to toss out another idea, it sounds like maybe the library/code
checking the response time doesn't have enough resolution, and it's
rounding up. 1/10th of a second is an odd place to stop resolution to
though. Bad multiplying or rounding?
I've seen people claim lots of 1ms responses when it turned out all of
the responses were in microseconds, they just didn't have enough resolution.
I will do strace for memcached later and post the results.
On Mar 2, 3:50 am, dormando <[email protected]> wrote:
What about memcached? Is it running on localhost or over the network?
Any chance you could get an strace from the memcached side? Have your test
app talk to a separate test instance or something.
Is it exactly or close to 0.10s each time? That's suspicious.
