This works for me using version 1.2.5 of the win32 version of memcached: http://lists.danga.com/pipermail/memcached/2007-July/004603.html
That is, you change the ImagePath value in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\memcached Server by just adding whatever parameters you want. Then you restart your service, and the new settings should be in effect. Also, remember that you can't look at the current memory usage of the memcached process, you have to execute the "stats" command and look at the value of the "limit_maxbytes" field if you change the max memory size and verify it. /Henrik Schröder On Fri, Oct 31, 2008 at 6:54 AM, Vipin <[EMAIL PROTECTED]> wrote: > > > Default memory is 64 MB. Check it in the help using memcached -h. > > So far no luck with changing registry keys. I dont seem to locate > egistry specifics to this setting. Anybody knows more details on > specific registry key path pls send those. > > On Oct 30, 9:38 pm, TheJonathan <[EMAIL PROTECTED]> wrote: > > Did you ever have any luck finding those registry keys with the > > configuration? Does anyone know what the memcached-Win32 uses as a > > default memory size if you just install it with "memcached.exe -d > > install"? > > > > On Oct 29, 11:24 am, "Vipin Kalra" <[EMAIL PROTECTED]> wrote: > > > > > > > > > I beleive it was all random. But I'll run it again couple of times > collect > > > my logs and will send you a copy of those. In my logs I am printing > both > > > keys and values for both success and failure cases. > > > > > On Wed, Oct 29, 2008 at 3:04 AM, Henrik Schröder <[EMAIL PROTECTED]> > wrote: > > > > Hi Vipin, > > > > > > The thing that happens is that the memcached server returns either > ERROR, > > > > SERVER_ERROR or CLIENT_ERROR, but I forgot to print out that message > in the > > > > default logger, so I don't know exactly what happens in your case. > > > > > > I've uploaded a new version to > > > >http://code.google.com/p/beitmemcached/downloads/listwhereit will > > > > actually print out the error it gets from the memcached server while > using > > > > the default logger. > > > > > > The reason you're seeing this error is because there is something in > either > > > > your key or your value that causes the entire request to become > invalid, and > > > > the client doesn't warn you about this like it should. Do you think > you can > > > > isolate the error and reproduce it, either by finding a key that > always > > > > gives this error, or a value that always gives this error? And if so, > can > > > > you send me that example so I can reproduce the error on my end? > > > > > > Or is the error completely random, such that a specific key and value > is > > > > sometimes stored ok, and sometimes not? > > > > > > /Henrik Schröder > > > > > > On Tue, Oct 28, 2008 at 9:21 PM, Vipin Kalra <[EMAIL PROTECTED]> > wrote: > > > > > >> hey Henrik, > > > > > >> Now I upgraded to version 1.2.6 and getting these error > intermitently > > > >> while while setting the data:- > > > > > >> ERROR BeIT.MemCached.ServerPool - Error in Execute<T>: localhost > > > >> at BeIT.MemCached.PooledSocket.ReadResponse() in > > > >> > C:\downloads\Memcached\BeITMemcached_source_2008_09_01\ClientLibrary\Pooled > Socket.cs:line > > > >> 149 > > > >> at > > > >> > BeIT.MemCached.MemcachedClient.<>c__DisplayClass1.<store>b__0(PooledSocket > > > >> socket) in > > > >> > C:\downloads\Memcached\BeITMemcached_source_2008_09_01\ClientLibrary\Memcac > hedClient.cs:line > > > >> 381 > > > >> at BeIT.MemCached.ServerPool.Execute[T](SocketPool pool, T > > > >> defaultValue, UseSocket`1 use) in > > > >> > C:\downloads\Memcached\BeITMemcached_source_2008_09_01\ClientLibrary\Server > Pool.cs:line > > > >> 136 > > > > > >> My key size is still less than 10K. > > > > > >> Any idea??- Hide quoted text - > > > > - Show quoted text -
