Hi,
I am trying to use mget() to get multiple data pieces using the C++
API. When it works the performance difference is great.
However, I seem to hit some sort of a communication hang when I have
about 5000 or higher key requests together.
Has anyone seen this issue earlier? Is there a size limi
> I am trying to use mget() to get multiple data pieces using the C++
> API. When it works the performance difference is great.
> However, I seem to hit some sort of a communication hang when I have
> about 5000 or higher key requests together.
What client is that, exactly? "The C++ API" isn't spe
Hi!
On Thu, Sep 29, 2011 at 7:47 AM, Prasad wrote:
> I am trying to use mget() to get multiple data pieces using the C++
> API. When it works the performance difference is great.
>
Is this the one in libmemcached? If so use the C API. The C++ API is just
there for a couple of folks who wanted
Hi,
Thanks for your responses.
Sorry, I should not have said C++ API. This was my wrapper over the
libmemcached C API, 0.43
Dormando, yes it is the binary protocol and I think what you mention
is exactly what might be happening.
The client seems to get stuck on send(). The read buffer you mention
> Hi,
>
> Thanks for your responses.
> Sorry, I should not have said C++ API. This was my wrapper over the
> libmemcached C API, 0.43
>
> Dormando, yes it is the binary protocol and I think what you mention
> is exactly what might be happening.
> The client seems to get stuck on send(). The read bu
Hi!
On Sep 29, 2011, at 2:07 PM, dormando wrote:
> Still, I thought this was fixed already. As a workaround you can chunk
> your multigets into smaller sections, but I thought that the client did
> support it
It does, so I would wonder how many total key requests are being sent.
Cheers,
-Br
Hi,
It starts getting stuck when I have a list of about 5000 keys in the
mget.
If I try to step and check which key is currently being sent ( when
the process is stuck ) its somewhere around the 2500 mark.
Is this fixed in 0.43 itself?
And so with this fix does the client call a fetch after a sma
Hi!
On Sep 29, 2011, at 2:30 PM, Prasad wrote:
> And so with this fix does the client call a fetch after a small chunk
> of multigets are reached inherently? Since I don't call the fetch till
> I return from the mget API call.
There is a water mark that causes the mget to go multi if it is too l
Hi Brian,
Sorry, I didn't have net access for a few days.
They keys were actually pretty simple since I was just doing some
basic testing.
they were of the form:
key[i] = xtoa(i)+"foo2";
Where i was just a loop variable ranging from 0 to 5000
Their lengths wouldn't exceed 10 characters.
Thanks,
