i would agree but trace shows delay:
this one by truss (freebsd strace)
76982: 2.532011750 0.099864927 poll({9/POLLIN},1,-1) = 1 (0x1) it
tooks 0.099seconds
and this one by strace
0.000061 [28b09d6f] poll([{fd=574240058, events=POLLIN|POLLPRI|
POLLRDNORM|POLLWRBAND|POLLERR|POLLNVAL|0x6000}], 1, INFTIM) = 1
([{fd=1933255265, revents=POLLIN|POLLPRI|POLLOUT|POLLHUP|POLLNVAL|
0x3a00}]) <0.098976>
also ~0.09 seconds.
both freezes on pool
On Mar 2, 4:27 am, Matt Ingenthron <ingen...@cep.net> wrote:
> 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 <dorma...@rydia.net> 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.
