> Hi there
>
> I am experimenting with using memcache for storing PHP sessions in a
> www cluster environment. But due to latency in network, I have noticed
> slight performance drop in application as opposed to just direct
> access.
>
> Has anyone played with changing MTU on their network card to
> Hi,
> I do simple benchmark on my web server by issuing 50 queries. I send
> 10,000 request and it shows by using memcached is slightly slower than
> (or almost the same) without memcached. The result shows 216.29
> request per second for memcached enabled and 216.51 for memcached
> disabled. How
> Hi Guys,
>
>
> I'm trying to compile memcached-1.4.4 in my IBM P550 machine running
> Linux RHE for Power PC64, but I'm getting the error:
>
> memcached-1.4.4]# ./configure
> checking build system type... Invalid configuration `powerpc64-unknown-
> linux-': machine `powerpc64-unknown-linux' not
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.
> 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 re
ne, rather than be thrown out as overhead when if a slab class
were to allocate a 1mb page.
So in memcached, a slab "page" is "however many chunks of this size will
fit into 1mb", a chunk is "how many chunks will fit into that page". The
slab growth factor determines how many slab classes exist.
I'm gonna turn this into a wiki entry in a few days... been slowly
whittling away at revising the whole thing.
-Dormando
> 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 cl
else, and they're logged in again? Does this mean
they found their original session again, or did you app log them in again?
-Dormando
On Fri, 12 Mar 2010, TheOnly92 wrote:
> I'm retrieving statistics via Memcache::extendedStats function, here
> are the basics:
>
> Sess
another placed and gets redirected to the home page
> (appears logged out for this page)
> 4. Refreshes and able to access the page again (logged in).
>
> On Mar 13, 1:35 pm, dormando wrote:
> > Can you telnet to the instances, type "stats", "stats items", an
for the
> purpose of session failover. So this restart could be
> done when operations could be *sure* that no tomcat will die.
Tomcat sounds like such a pisser :P Even with your backup thing I'd
probably still add an option to allow it to journal to a database, and I
say this knowing how to get every last ounce of efficiency out of
memcached.
-Dormando
> Is there anyway to get the keys of the largest objects currently in my
> memcached? I'm not concerned about locking up the server. I just wish
> to be able to run a command one time which will give me the key of the
> biggest objects that are currently stored.
>
> Thanks
You could use peep or so
he last_accessed time isn't being
updated with the synced time).
- At some point background process or whatever DELETE's expired crap from
the DB.
So you still do some writes, but it should be vastly reduced compared to
updating the "last accessed" timestamp on every view, and reads against
the DB should almost never happen for active sessions that stay in cache.
Given the addition of the ADD bit, I guess you could build it so that in a
pinch you could just shut off DB journaling to deal with some overload
scenario.
-Dormando
> Hi, I'm getting segfault just after running the memcached n Fedora 8,
> runnin in the VMWare.
>
> I just run
> # /usr/local/bin/memcached -u gri -m 1 -v
> in one console
> # telnet localhost 11211
> in another, and in the 1st get endless flow of
> "Catastrophic: event fd doesn't match conn fd!"
1.4.6, and are
stabilizing 1.6.0 for release. More of the rest of the open bugs will be
closed out for 1.4.6.
A number of us will be at MySQLConf (http://en.oreilly.com/mysql2010/)
next week. Speaking, dotorg-boothing, or getting drunk in the lobby. Come
say hi if you're brave enough.
-Dormand
running a test
using a pure client (ruby or whatever, just no libmemcached) over
localhost to see if you can reproduce the issue there.
thanks,
-Dormando
On Wed, 7 Apr 2010, Ryan Tomayko wrote:
> We have a few memcached machines doing ~1000 ops/s (9:1 get to set)
> each. These are fairly b
> memcached 1.4.0 amd64 built from custom debian package
> memcached ruby lib is 0.17.3 (bundles libmemcached 0.32)
>
while you're in there, any chance you could test 1.4.5? Some stuff's been
fixed since.
--
To unsubscribe, reply using "remove me" as the subject.
> I thought this was a FAQ -- or at least I have memory of this being discussed
> here before.
>
> I have one process that uses memcached for throttling by setting a key with a
> timeout. If the set fails (NOT_STORED, as the FAQ describes)
> then the process waits.
>
> The question came up yeste
ayout sucks a lot less. As always I/we're open to feedback.
if you would like to contribute too, ask for wiki bits. If you're going to
complain, we (or you) might as well fix it.
It's our goal to make this clear and thorough for anyone who wishes to get
started with memcached.
-Do
> I installed memcached almost a week ago on a site that gets quite some
> traffic and these are my stats:
>
> 48944634 Hits
> 68 Misses
> 25 (2869804) Current Items(total)
>
> Free: 63.9 MBytes (99.8%)
> Used: 127.8 KBytes (0.2%)
>
> Is this even possible? I would say it's working just based on th
On Sat, 17 Apr 2010, wminside wrote:
> Hi, I'm using memcache.php by Harun Yayli
Verify with another tool, or telnet to the server and run 'stats'. paste
the output to the list if you need help, and the wiki covers some stuff
too.
curr_bytes / limit_maxbytes gives the "fill rate", but isn't ne
> STAT version 1.2.8
Consider upgrading to 1.4.x ;)
> STAT curr_items 25
You have at most 25 items in your cache. that sounds pretty small.
> STAT bytes 130845
Yeah, that's 128k. Your app's just not using the cache very much.
-Dormando
--
Subscription settings: http:
On Sat, 17 Apr 2010, wminside wrote:
> I get memcached from the EPEL repository.
>
> Can I set a higher current items? I mean, is there anything I can do
> to get memcached use more memory or it's just how vBulletin works.
Go whine at the vB authors about putting some real shit into the cache.
Ding. You have access.
On Tue, 20 Apr 2010, Xaprb wrote:
> Can someone give me SVN commit rights so I can add a reference to
> http://code.google.com/p/mysql-cacti-templates/wiki/MemcachedTemplates
> to the wiki? My Google Code username is baron.schwartz.
>
> - Baron
>
>
> --
> Subscription sett
ing* a mutex lock, and would thus crash
sometimes. So they were afraid of running stats commands. That bug hasn't
existed for three years at least.
-Dormando
on available from
> the project team that explains the monitoring aspects of memcached? Such as
> the methods of receiving stats (if there are any aside from getStats())?
>
>
> -Original Message-
> From: memcached@googlegroups.com [mailto:memcac...@googlegroups.com] On
>
> Actually sorry I should've been more descriptive. I plan on using a java
> client to get the stats from memcached so that we can eventually pipe the
> stats to our monitoring software. What would be the best java client?
> Spymemcached?
Probably, yes.
> Also, is there any consideration in the
Whaaat.
What platform / os / compiler? can you pastebin or attach your full
'stats' / 'stats items' / 'stats slabs' info?
On Wed, 26 May 2010, diez wrote:
> Hello all,
>
> I'm using Memcached version 1.4.4 and built a script to measure the
> "wasted bytes" from the "stats slabs" information
> We're building a system with heavy real-time write volume and looking
> for a way to decouple db writes from the user request path.
>
> We're exploring the approach of buffering updated entities in
> memcached and writing them back to the database asynchronously. The
> primary problem that we're
> We're currently using PHP's memcached library (http://us2.php.net/
> memcached).
>
> We have two memcached servers but one of them, during heavy traffic
> times starts seeing a significant ping time increase, up to 200-400ms
> just to ping the server. Our memcached server's log says:
> "Failed t
This smells like you're configuring your clients wrong... The client list
must be _exactly the same_ on every app server. Don't reorder them or put
"localhost" in there.
It's also possible that appserv2 can't reach one of the memcached daemons
as well, and is putting keys on the only available ser
> I'm debugging an application (PHP witch pecl memcache) to see why
> there is a small percent of timeouts when connecting to memcached.
> Everything seemed to be ok until today where I found these values of
> total_connections:
>
> STAT uptime 2174031
> STAT curr_connections 34
> STAT total_connec
>
> Any thoughts on what might be going on here?
>
> As for vitals/system config:
>
> Here's a recent stats dump:
> STAT pid 19986
> STAT uptime 8526687
> STAT time 1277416425
> STAT version 1.2.8
You should probably upgrade, but I think this version has what you may
need...
If you can reproduce
e memcached instances on 10gbps ethernet servicing small
requests. I'm sure there's someone out there like that, but I doubt anyone
listening to the FUD would be one of them.
-Dormando
orward less accurately when
something does go wrong.
- Use some anti-clock-skew magic that maybe libevent uses. Need to
research more options :P
Anyone care? The increase in the number of these types of reports is
getting obnoxious, and cloud computing's god-awful-ness can only make it
worse.
-Dormando
>
> Great analysis, and exactly the sort of case studies we'd like to see at
> Surge this year. We haven't received any memcached-related CFPs yet. I
> hope the community sees this and someone attempts to rectify it. :)
>
> http://omniti.com/surge/2010/cfp
Unfortunately, baltimore's a bit far f
ss them and produce a
> response with a body, reaching up to 500k requests/second even on higher grade
> hardware with multiple interfaces sounds pretty good to me.
For most hardware memcached is limited by the NIC. I'd welcome someone to
prove a simple case showing otherwise, at which time we'd prioritize an
easy fix :)
-Dormando
> >
> > For most hardware memcached is limited by the NIC. I'd welcome someone to
> > prove a simple case showing otherwise, at which time we'd prioritize an
> > easy fix :)
>
> Does that mean you should use multiple NICs on the servers and spread the
> clients over different networks?
It means yo
anything with it.
There're dozens of real problems to pick on us about - I sorely wish
people would stop hyperfocusing on the ones that don't matter. Sorry if
I've picked on your favorite memcached alternative; I don't really care
for a rebuttal, I'm sure everyone's working on fixing their problems :P
-Dormando
> Dormando... Thanks for the response. I've moved one of our servers to use an
> upgraded version running 1.4.5. Couple of things:
> * I turned on logging last night
> * I'm only running -vv at the moment; -vvv generated way more logging than
> we could handle. As
> Hi guys,
>
> I was wondering,
> If I have an array of 10 machines , 1 instance per machine set up like
> this:
>
> "instances" => array(
> "server1" => array("host" => "111.111.111.111",
> "port" => "11211",
> "weight" => 6),
> "server2
ould make it impossible to alter
> the hashing distribution).
>
> I'll report back what I find - thanks for your continued input!
>
> -Darryl
>
>
> On Thu, Jul 1, 2010 at 12:28 PM, dormando wrote:
> > Dormando... Thanks for the response. I've
Here's a more succinct and to the point page:
http://code.google.com/p/memcached/wiki/NewUserInternals
^ If your question isn't answered here ask for clarification and I'll
update the page.
Your problem is about the slab preallocation I guess.
On Tue, 6 Jul 2010, Matt Ingenthron wrote:
> Hi Ser
traffic patterns or code pushes.
Sometimes high eviction rates can mean you're shoveling in too many items
that're never fetched again (but still set to expire after a long time).
So it's a matter of watching these stats + being dilligent about what your
app is doing.
Would you mind opening a bug report about the evictions + flush_all thing?
that's an easy fix.
Thanks,
-Dormando
em swapping, or your box is otherwise
overloaded. also depending on how you're measuring it your client box/etc
could be slightly broken.
-Dormando
On Sun, 11 Jul 2010, Snehal Shinde wrote:
> Yes Jay is right. My server and client config are in sync. The problem
> is only intermittent and so i felt maybe increasing the default
> timeout might help. Any idea how i can increase the default memcache
> timeout for the php client Memcache?
I fo
On Mon, 12 Jul 2010, Snehal Shinde wrote:
> I am using the stable 2.x one. I have set the timeout to 3 secs now. Lets see
> how that goes
> Snehal
You might want to stick with 2 or 4 seconds to test :) putting it right on
the line with the SYN timeout will still give you inconsistent results...
tradeoff here. We try hard to only provide features that people
can't easily bite their feet off with, and saying this would be useful for
production folks probably isn't true :(
Any thoughts/rebuttals?
-Dormando
> switched to 4 secs now. also if its a packet loss issue will it make sense to
> reduce the $retry_interval from the default 15 secs to say 2
> secs? http://us2.php.net/manual/en/memcache.setserverparams.php
> also the error that i get intermittenly is "COULD NOT CONNECT TO SERVE". Is
> there
> Greetings,
>
> We are a small company who are increasingly relying on
> memcached for our big projects. We are very pleased with
> its performance.
>
> I've put this patch that
>
> 1) chroots to /var/empty
> 2) change from root to a simple user.
>
> It effectively jails the process once it no lo
exploit, he cannot execute commands like /bin/sh, since
> he's jailed inside the /var/empty.
>
>
> //Logan
> C-x-C-c
> On Tue, Jul 20, 2010 at 2:38 AM, dormando wrote:
>
> > Greetings,
> >
> > We are a small company who are inc
gt;pw_gid, pw->pw_gid, pw->pw_gid) ||
> + setresuid(pw->pw_uid, pw->pw_uid, pw->pw_uid)) {
> + fprintf(stderr," failed to switch to correct user");
> + exit(EX_NOUSER);
> + }
> +
>
Huzzah!
On Mon, 19 Jul 2010, Patrick Galbraith wrote:
> Hi all!
>
> I'm pleased to announce the release of Cache::Memcached::libmemcached 0.02011
> and Memcached::libmemcached 0.4201. Cache::Memcached::libmemcached uses
> Memcached::libmemcached, which is a Perl wrapper for libmemcached, which is
he client object wrong and getting out of sync with the
protocol. Or the client's just buggy...
Sorry, don't have any ideas about what it could be in particular. make
sure you're sending keys that don't have newlines/spaces/etc in them and
that you're not clobbering the object somehow.
-Dormando
http://code.google.com/p/memcached/wiki/NewServerMaint#Looks_Can_be_Deceiving
Think I'll write a separate page about managing memory, based off of the
slides from my mysqlconf presentation about monitoring memcached...
We're not ignoring you, the patch is against what the LRU is designed for.
Sev
om the
> cluster, while monitoring memory gives you perfectly accurate info.
>
>
> On Fri, Jul 23, 2010 at 12:12 AM, dormando wrote:
>
> http://code.google.com/p/memcached/wiki/NewServerMaint#Looks_Can_be_Deceiving
>
> Think I'll write a separate page about ma
> On Fri, Jul 23, 2010 at 8:47 AM, dormando wrote:
> I tried.
>
> Try the engine branch?
>
> I guess, I'll have to at some point.
>
> Just wanted to say, that LRU was designed as an algorithm for a uniform cost
> model, where all elements are almost
On Sun, 25 Jul 2010, Jakub Łopuszański wrote:
> Thanks for an explanation.
> I see that we have entirely different points of view, probably caused by
> totally different identified sets of bottlenecks, different
> usage, different configurations etc (I assume that you have greater
> experience
> It seems that memcached does not comply with the memcached protocol
> regarding multi gets. In particular it seems that given a series of
> getq it will respond to them without being uncorked by a non quiet
> command. Am I correct that this is the implemented behavior? And if so
> do you know of
On Thu, 29 Jul 2010, j.s. mammen wrote:
> Folks, lets not get bogged down by REST defined by Roy Fielding in
> 2000.
>
> My question was simple.
> Here it is again, rephrased.
>
> Do we need to implement a memcached layer whereby we can access the
> cached objects by using HTTP protocol. Here i
On Sat, 7 Aug 2010, Dustin wrote:
>
> On Aug 7, 7:52 am, Loganaden Velvindron wrote:
> > There seems to be a problem when I pasted it in gmail.
> >
> > Here's a link to the git diff:
> >
> > http://devio.us/~loganaden/memcached.git.diff
>
> This makes some sense to me. That functionality is
Can you resubmit as a unified diff?
On Tue, 17 Aug 2010, ilnarb wrote:
> I suggest you to eliminate taking of the lock on cqi_freelist.
> In order to it we should done all work on cqi_freelist by one thread
> -- dispatcher thread in memcached.
> I made some changes in queue code, including improv
sto
On Wed, 18 Aug 2010, Chad wrote:
> I am trying to find a way to check if the memcachedclient is still
> alive or not but it seems to be there is no public api for me to do
> so. Can someone clarify this?
>
> Thanks.
> Chad
>
On Wed, 18 Aug 2010, Matt Ingenthron wrote:
> dormando wrote:
> > sto
> >
>
> I'm pretty sure he sent it only once. I think this is a problem with Google's
> SMTP and MTAs if I recall correctly.
ense for what memcached is, and I'd like to see an option in 1.4.x for
enabling such behavior to test with.
That avoids the issue in another way entirely, but I think we'll need both
fixes :P
-Dormando
d to handle such case in
> application,
> don't you?
(repeating from IRC for posterity): I like shoving an "ERROR: Too many
connections" down the pipe before closing it. Gives client authors the
chance to throw useful errors for the developer. Otherwise it's likely to
manifest as failed gets/sets with no errors.
-Dormando
Expire time turns into a unixtime date after 30 days. It's in the protocol.txt
but possibly overlooked in the wiki :(
On Aug 26, 2010, at 8:19 PM, kedy211 wrote:
> It's unusually the question I mentioned in the topic. And, I can NOT find the
> offical answer from wiki.
>
> Sometime, I set the
We're still working on merging down 1.6... but if this exists outside as
an engine nothing of us blocks you from using it for now.
I sort of wonder a little about outright pulling it into the tree, since
that implies we have to maintain it.
On Fri, 27 Aug 2010, KaiGai Kohei wrote:
> BTW, how abo
ngine.so module. :-)
>
> Thanks,
>
> On 8月27日, 午後6:02, dormando wrote:
> > We're still working on merging down 1.6... but if this exists outside as
> > an engine nothing of us blocks you from using it for now.
> >
> > I sort of wonder a little about outright
Upgrade back to 1.4.5 and look for the 'listen_disabled_num' value in the
stats output. If the number is increasing, you're hitting maxconns.
If not, you're probably seeing packet loss, or have a firewall in the way
that's maxing out.
On Tue, 7 Sep 2010, the_fonz wrote:
> Guys,
>
> We are seeing
Uhhhm.
memcached-init is from:
commit 4b1b1ae76ef6e78dd3f1d753931ac8051ae99e9a
Author: Brad Fitzpatrick
Date: Tue Dec 30 19:56:33 2003 +
I assume brad copied the skeleton files and modified it. IANAL so I'm not
sure how much of it had to be changed to be able to flip the license, but
it s
> Perhaps this is more a question about application design then directly about
> Memcached.
>
> I have a very large and somewhat slow data fetch from a back-end service.
> The client doesn't need all the data at the same time so the plan is to split
> it up into parts and save into Memcached to
> We have an 2 x quad core server with 32 gb ram. If many clients
> connect to this server (only memcached runs on it) the first core run
> to nearly 100 % use by si (software interrups) and so some client
> can't reach the server.
> Memcached runs currently with 4 threads and with version (1.4.2).
Sep 2010, Jay Paroline wrote:
> We've run into this exact same issue and narrowed it down to the NIC,
> but don't really know where to go from there. I'm going to look up
> Dormando's suggestions but if anyone else has experience with this and
> can point us in the r
>
> I have a memcached server in a production environment that is showing
> a strange behavior :
> bytes_written grows fast (~1.2Mo per second), but the number of
> cmd_set does not change!
>
> How is that possible?
The bytes_* values refer to bytes written/read to the network. fetches/etc
will t
fferent slab sizes, memcached will
> not allocate more pages for the particular slab size, causing
> premature evictions. This is particular evident since our application
> has lots of large objects that require lots of pages.
>
> From the wiki by dormando...
>
> The previous chunk-
similar issues.
So here it is (public domain) along with a wiki page on how to use it.
-Dormando
We took it out for a reason, + if you run with -t 1 you won't really see
contention. 'Cuz it's running single threaded and using futexes under
linux. Those don't have much of a performance hit until you do contend.
I know some paper just came out which showed people using multiple
memcached instan
em, each
> with a dual socket Xeon X5570 and 2x Myri-10G NICs that I was planning on
> using for tests. Would you be so kind to tell me if
> there's any standard performance test suite for memcached that is typically
> used? Or should I just write my own trivial client---in part
all the memory is...
I prefer setting swappiness to 0 and vfs_cache_pressure to 200 or
similar... ie; really really deprioritize filecache over application
memory.
I assume you'll find a bunch of socket memory used in the slabinfo. People
tend to forget that TCP connections use buffers.
-Dormando
lures?
That should help rule out anything to do with protocol errors or other
client issues.
-Dormando
>
> well, I just used this tool to force enough requests :)
>
> ok, I extended it a bit, for generating min/max/avg times of the
> processes,
> and for executing an explicit memcache get.
> If you like, You can adopt my patches for redistribution:
>
> http://www.maiers.de/memcache/mc_conn_tester.pl
> no it dit not. only once per some hours.
>
> at the moment my test script it puts out something like
> Averages : (conn: 0.00028186) (set: 0.00017516) (get: 0.00014979)
> Min : (conn: 0.00018787) (set: 0.7915) (get: 0.5698)
> Max : (conn: 0.01806998) (set: 0.01937985) (get: 0
> Hi everyone,
>
> we have the following situation: due to massive simultaneous inserts
> in mysql on possibly identical primary keys, we use the atomic
> memcache add() as a semaphore. In a few cases we observed the
> behaviour, that two simultaneous add() using the same key from
> different clien
> our 50+ consistent hashing cluster is very reliable on normal
> operations, incr/decr, get, set, multiget, etc. is not a problem. If
> we have a problem with keys on wrong servers in the continuum, we
> should have more problems, which we currently have not.
> The cluster is always under relative
>
> Yeah, right. :-) Restarting all memd instances is not an option. Can
> you explain, why it is not possible?
Because we've programmed the commands with the full intent to be atomic.
If it's not, there's a bug... there's an issue with incr/decr that's been
fixed upstream but we've never had a re
> On 14 Okt., 10:31, dormando wrote:
> > > Yeah, right. :-) Restarting all memd instances is not an option. Can
> > > you explain, why it is not possible?
> >
> > Because we've programmed the commands with the full intent to be atomic.
> > If it's
I think you're supposed to read to the point where it says "queues stuff
in memory before sending to the server" and extrapolate that writing to
the queue too fast is a bad thing.
On Sun, 17 Oct 2010, Shi Yu wrote:
> Kelvin.
>
> This is year 2010 and computer programs should not be that fragile.
heck "bytes" and it shows the memory size is over
> 4MB.
> Could you help to clarify what is going on?
> Thank you.
The lowest the memory limit can go is about 48M. It ignores anything
lower.
-Dormando
soon [tm]
On Tue, 19 Oct 2010, Pavel Kushnirchuk wrote:
> Folks,
>
> May be anybody know, when will be a next planned release of memcached.
> Especially I am interested in a release of Win32 branch.
>
>
ull.
On Wed, 20 Oct 2010, yashushi wrote:
> Hi Dormando,
>
> We have tried the setting with 48MB and 64MB, but the same problem
> still comes out.
> Please kindly help to clarify.
> Thank you.
>
> -Yashushi
>
>
> On 10月18日, 下午4時50分, dormando wrote:
> > > H
alhost is faster" but it's more than adequate over the network.
-Dormando
reclaims are good, evictions are bad
On Thu, 4 Nov 2010, Kate Wang wrote:
> We are experiencing high reclaims instead of evictions. Could slab
> distribution shift cause that as well?
>
> If the slab distribution shifted could cause high eviction rate, what's the
> best way to fix it or avoid i
It's `build-essential`, iirc.
On Sun, 14 Nov 2010, Steven Veneralle wrote:
> hey Alex. for some reason Debain doesnt find that package. i am literally
> coming off a fresh instal plus Im having to do everything n CLI remotly
>
> On Sun, Nov 14, 2010 at 2:42 PM, Alex Miller
> wrote:
> Hi
you have allocated per size and how
> >> many items are there. I guess this should give you good idea what is
> >> really happening.
> >>
> >> :- )
> >>
> >> art
> >>
> >>
> >>
> >> On 5 November 2010 05:59, vishnu wro
> So, pretty general question:
>
> Seems against the recommendation of this list, Memcached is often used as a
> session store. I'm working with a client now that uses two clusters of
> memcached servers and every write is saved on two
> clusters and on failed reads the backup is read. Poor man
Think we worked this out on IRC, there was some thing running flush_all
over and over on his server.
On Fri, 21 Jan 2011, Ivan wrote:
> Hello,
>
> i have memcached 1.4.5 on Centos 5.5, my sets seem to expire (no
> matter what i put as expire time, infinite or 5mins 1 hour etc) after
> few seconds
> Thanks, we kind of understood that already. I'm just wondering, what
> behaviour would I expect to see from the client? What is the R limit exactly?
> For instance, if I send a multiget with more than the R limit it doesn't
> result in a connection yield, even if I send a large quantity
> conc
> Hi to all,
>
> First of all please accept my apologies if this question answered
> before.
> I've searched for a straight answer but I couldn't find one. Maybe I'm
> not looking in the right place.
>
> So, I've started using the memcached for user sessions and I back it
> up with a database stora
> problem:
> today i need 4 packets to make 'lock'/'unlock' using memcache
> i need to use less ROM/CPU/RAM/network at client side
>
> solution:
> 1) make server side lock function with 2 packet (with atomic operations)
> 2) make a proxy if function = lock/unlock, proxy make these packets to
> serv
ltiget to memcached asking for all of the
PIC ids, and processes any that it gets back (get key_1 key_2 key_3 etc)
Then there's no locking, and multiple PIC's can use memcached in parallel?
That sounds like a win/win to me, if gross :)
-Dormando
1 - 100 of 1190 matches
Mail list logo
