Comment #2 on issue 125 by i...@quintura.com: Compile error with gcc
http://code.google.com/p/memcached/issues/detail?id=125
Thanks for answer.
Memcached has compiled correctly with ./configure CC=gcc-4.3.
You can close this ticket.
I have some errors, when i tried with ./configure CC=gcc-4.4
Here is our current setup:
webserver1 (also runs session memcache server)
webserver2 (also runs session memcache server)
database (specialized memcache storage for data caching)
We are not really a high loaded site, at peak time only about 1500
users online together. Network is not really
We make liberal use of the namespace option to
Cache::Memcached::libmemcached, creating one object for each of our
dozens of namespaces.
However I recently discovered that it will create new socket
connections for each object. i.e.:
#!/usr/bin/perl -w
use Cache::Memcached;
use strict;
We discovered this as well a few months ago... I don't think we found a
workaround :(
Maybe someone else has?
On Fri, 12 Mar 2010, Jonathan Swartz wrote:
We make liberal use of the namespace option to
Cache::Memcached::libmemcached, creating one object for each of our
dozens of namespaces.
Ok, that seems correct for me. Your described issue still sounds for
me like a connection problem.
On which interface is your memcached bound (memcached.conf?)? Does a
telnet 172.23.111.11 11211
work from every webserver instance? I could imagine following
scenario:
User1 opens a session on
On Mar 11, 9:01 pm, Les Mikesell lesmikes...@gmail.com wrote:
On 3/11/2010 1:01 PM, Martin Grotzke wrote:
Hi,
I'm trying to follow this thread on my mobile, i hope i didn't miss
anything. But AFAICS it was not yet explained, when memcached might
drop cached data as long as there's
On 3/12/2010 11:21 AM, martin.grotzke wrote:
Hi,
I'm trying to follow this thread on my mobile, i hope i didn't miss
anything. But AFAICS it was not yet explained, when memcached might
drop cached data as long as there's enough memory and expiration is
not reached. Or is this not
I'm using memcached to store these data:
- user object - an java object consisting of username, password,
city...;
- user status info;
- counter,
so for every user login, I will make three memcached put operation.
After making 10.000 logins, I have these stats via memcached stats:
bytes - ~1Mb
Hi,
I know that this topic is rather burdened, as it was said often enough
that memcached never was created to be used like a reliable datastore.
Still, there are users interested in some kind of reliability, users
that want to store items in memcached and be sure that these items
can be pulled
I just started a new thread How to get more predictable caching
behavior - how to store sessions in memcached to discuss my more
general question on how to achieve more predictability/reliability (I
might have hijacked this thread a little bit, sorry for this).
Cheers,
Martin
On Mar 12, 6:43
I believe most of this is covered in
http://dormando.livejournal.com/495593.html
Jared
On Mar 12, 9:02 pm, martin.grotzke martin.grot...@googlemail.com
wrote:
Hi,
I know that this topic is rather burdened, as it was said often enough
that memcached never was created to be used like a
The way I would solve this would be to change
Cache::Memcached::libmemcached to *contain* a Memcached::libmemcached
object (go from ISA to HAS-A), and forward all methods appropriately.
Then multiple C::M::l objects could share the same M::l object.
Other than the ref() of the object,
With my question how do I have to run memcached to 'store' these sessions
in memcached I was not referring to a general approach, but I was referring
to the concrete memcached options (e.g. -n 204800 for 200kb slabs) to use.
The post you mentioned is very high level and does not answer my
The resounding answer you will get from this list is: You don't, can't
and won't with memcached. That is not its job. It will never be its job.
Perhaps when storage engines are done, maybe. But then you won't get the
performance that you get with memcached. There is a trade off for
On 3/12/2010 5:10 PM, Martin Grotzke wrote:
With my question how do I have to run memcached to 'store' these
sessions in memcached I was not referring to a general approach, but I
was referring to the concrete memcached options (e.g. -n 204800 for
200kb slabs) to use.
The post you mentioned is
Hi Brian,
you're making a very clear point. However it would be nice if you'd provide
concrete answers to concrete questions. I want to get a better understanding
of memcached's memory model and I'm thankful for any help I'm getting here
on this list. If my intro was not supporting this please
Part of the disconnect is that, how do I have to run memcached to
'store' these sessions in memcached, is not a concrete question. It's
wibbly wobbly at best to try and achieve this behavior, and, You
can't, _is_ concrete in that there is no way to do this in a
mathematically provable way. The
Hi,
Alexandre Ladeira wrote:
I'm using memcached to store these data:
- user object - an java object consisting of username, password,
city...;
- user status info;
- counter,
so for every user login, I will make three memcached put operation.
After making 10.000 logins, I have these stats via
Here is our current setup:
webserver1 (also runs session memcache server)
webserver2 (also runs session memcache server)
database (specialized memcache storage for data caching)
We are not really a high loaded site, at peak time only about 1500
users online together. Network is not really
Hi Les,
On Sat, Mar 13, 2010 at 12:29 AM, Les Mikesell lesmikes...@gmail.comwrote:
On 3/12/2010 5:10 PM, Martin Grotzke wrote:
With my question how do I have to run memcached to 'store' these
sessions in memcached I was not referring to a general approach, but I
was referring to the
I'm trying to get a better understanding of how memcached works. I'm
starting with a simple example here to see how this could be handled. The
numbers are just taken for example, if I didn't mention this already. When
this simple example is ok, more complexity is added and numbers change.
Still, I
Some details here:
http://dev.mysql.com/doc/refman/5.0/en/ha-memcached-using-memory.html
thanx for this link. Some details in the text are confusing to me. It says:
When you start to store data into the cache, memcached does not
allocate the memory for the data on an item by item
The memory allocation is a bit more subtle... but it's hard to explain and
doesn't really affect anyone.
Urr... I'll give it a shot.
./memcached -m 128
^ means memcached can use up to 128 megabytes of memory for item storage.
Now lets say you store items that will fit in a slab class of
dormando wrote:
To be most accurate, it is how many chunks will fit into the max item
size, which by default is 1mb. The page size being == to the max item
size is just due to how the slabbing algorithm works. It creates slab
classes between a minimum and a maximum. So the maximum ends up
On Mar 12, 6:10 pm, Les Mikesell lesmikes...@gmail.com wrote:
So what happens when a key is repeatedly written and it grows a bit each time?
I had trouble with that long ago with a berkeleydb version that I think was
eventually fixed. As things work now, if the new storage has to move to a
I'm retrieving statistics via Memcache::extendedStats function, here
are the basics:
Session Server 1
Version 1.2.2
Uptime 398,954 sec
Cache Hits 2,065,061
Cache Misses987,726 (47.83%)
Current Items 381,928
Data Read 4,318,055.02 KB
Data Written2,011,004.09 KB
Current
Can you telnet to the instances, type stats, stats items, and stats
slabs, then copy/paste all that into pastebin?
echo stats | nc host 11211 stats.txt works too
You version is very old... It's missing many statistical counters that
could help us diagnose a problem. The extendedstats isn't
27 matches
Mail list logo
