On Jun 9, 11:58 am, Eduardo Silvestre wrote:
> Hello Adam,
>
> it's possible deallocate memory on the fly ?
It is generally not possible to return memory to the system (from
malloc using sbrk anyway).
You don't need to, though. Give memcached as much memory as you
think it should have. D
Hello Adam,
it's possible deallocate memory on the fly ? Did i need change something ?
Or upgrade memcache version ?
Regards,
On Thu, Jun 9, 2011 at 5:20 PM, Adam Lee wrote:
> why do you need to restart it? you're telling it that it's allowed to use
> up to 2G and it never breaks that... fl
why do you need to restart it? you're telling it that it's allowed to use
up to 2G and it never breaks that... flush_all only flushes the cache, it
doesn't deallocate memory.
awl
On Jun 9, 2011 6:30 AM, "Eduardo Silvestre" wrote:
> Hello,
>
> every weeks we need restart memcached daemon... I tr
your email and your pasted stats seem to greatly disagree... you're
allocating 96MB for memcached and that's how much it thinks it's stored. it
also says it has stored 630k items- where are you getting 2,600?
also, as an aside, does your test program only store one size of item?
awl
On Jun 8, 2
PK -
Just a side point here, but:
> memcached -d -m 96 -n 10 -c 4096 -f 1.05 -l 127.0.0.1 -p 11211
*-m *Use MB memory max to use for object storage; the default is
64 megabytes.
*-c *Use max simultaneous connections; the default is 1024.
So, my question is, you're starting memcached on a ser
Hello,
every weeks we need restart memcached daemon... I try do flush_all with no
lucky. Do you know other command to flush ?
nobody 1 0.1 6.8 586716 564768 ? SJun06 5:45
/usr/bin/memcached -m 2048 -p 11211 -u nobody -l 192.168.52.52 -c 64000 -M
stats
STAT pid 1
STAT up
Actually I joined this google group to ask the same thing, and found this
thread.
I start memcached on a CentOS 64 bit server with 8 GB of RAM, with the
following settings:
memcached -d -m 96 -n 10 -c 4096 -f 1.05 -l 127.0.0.1 -p 11211
Yet, the memcached on my server has just about 2,60
> Hello Dormando,
>
> thans for your feedback. In fact i'm using the last stable version at debian
> repositories (http://packages.debian.org/lenny/memcached). Why will no
> longer accept new connections? Can i determine the cause based on stats?
>
> I'm collecting data from memcache with cacti
> In fact i'm using the last stable version at debian repositories
> (http://packages.debian.org/lenny/memcached).
Then also upgrade your OS to Squeeze (latest stable) :)
http://packages.debian.org/squeeze/memcached
- Marc
On Mon, May 30, 2011 at 6:12 AM, Eduardo Silvestre wrote:
> Hello Dorma
I don't know if possible maybe you have Apache threads mounting up on web
servers to the default limit of 1024 sockets on the memcached? Used to
happen to us a few times on DB timeouts.
We also used to have crashes of memcached from time to time so maybe buggy
version?
Art
On May 30, 2011 11:12 P
Hello Dormando,
thans for your feedback. In fact i'm using the last stable version at
debian repositories (http://packages.debian.org/lenny/memcached). Why will no
longer accept new connections? Can i determine the cause based on stats?
I'm collecting data from memcache with cacti templates, an
> Hello everyone,
>
> every weeks my memcache server stop accepting more connections. Today
> before restart daemon, i've check stats.
>
> stats
> STAT pid 30026
> STAT uptime 938964
> STAT time 1306667508
> STAT version 1.2.2
Please upgrade to a newer version :) That one has grown a lot of hair,
Hello everyone,
every weeks my memcache server stop accepting more connections. Today
before restart daemon, i've check stats.
stats
STAT pid 30026
STAT uptime 938964
STAT time 1306667508
STAT version 1.2.2
STAT pointer_size 64
STAT rusage_user 682.422648
STAT rusage_system 1636.058247
STAT curr
13 matches
Mail list logo
