had to disable signups. If you're still around
or have any idea on where or how to spread the word of this thing, please
do. It's been a lot of work and I'd like to get some more folks using it.
Thanks!
-Dormando
--
---
You received this message because you are subscribed to the Google Groups
81428
STAT crawler_reclaimed 1162226
STAT crawler_items_checked 5028977899
STAT lrutail_reflocked 8635
STAT moves_to_cold 5373497
STAT moves_to_warm 4364867
STAT moves_within_lru 3173096
STAT direct_reclaims 0
STAT lru_bumps_dropped 0
ENDOn Monday, September 4, 2023 at 11:53:10 PM UTC+3 dormando
Hey,Can you include the output from "stats"?Connections have nothing to do with CPU/memory/disk space(??). There's a connection limit (-c) you're running into. The stats output will list the connection limit and if connections have been rejected because of it.On Sep 4, 2023, at 1:14 PM, Ahmet
rder to retrieve the value of the key.This work for all slabs except the last one. Is there any way to programmatically retrieve the data ?Thanks,Bob. On Tuesday, June 6, 2023 at 11:22:44 PM UTC+3 dormando wrote:Hey,
Items larger than the slab class max are "chunked" across multiple slab
chun
cy. Making the "max slab class" smaller means
we can make better use of the slab classes. At some point I will be
reducing the default setting from 512k to 256k or lower, but I need to
revisit it and add some stats counters first.
-Dormando
On Tue, 6 Jun 2023, boaz shavit wrote:
> Hello
effective.BestJavier AriasOn Sunday, April 23, 2023 at 7:24:28 PM UTC+2 dormando wrote:Hey,
Thanks for reaching out!
There is no crash safety in memcached or extstore; it does look like the
data is on disk but it is actually spread across memory and disk, with
recent or heavily accessed data staying
. I'd be happy
to go over a few scenarios if you'd like.
-Dormando
On Sun, 23 Apr 2023, 'Danny Kopping' via memcached wrote:
> First off, thanks for the amazing work @dormando & others!
> Context:
> I work at Grafana Labs, and we are very interested in trying out extstore for
>
Hey,Uhh well I can say I'm from the USA. I'm pretty sure Brad is too. Probably the rest is accurate.Probably worth noting the other three haven't contributed in over ten years.On Mar 10, 2023, at 1:52 PM, Jonathan Louie wrote:Hello,Software being used by my organization is being reviewed,
Hey,
That old "item_cachedump" command is deprecated. The locking is fine; it's
actually only looking at the COLD_LRU instead of walking all of them like
the lru_crawler.
I'd rather remove the command entirely than do any further work on it; it
has a hard limit on how many keys it can dump, it
Hey,
Sometimes newer compilers are more strict.
What version are you trying to build? Did any previous version work or
does everything fail on Fedora 37?
I don't know about that evutil_socket_t error though.
On Tue, 14 Feb 2023, Slawomir Pryczek wrote:
> Hi Guys, any idea why building is
Hey,
Just store more data and that ratio will rise. I don't know why that stat
is named "memory efficiency". You have a lot of RAM free.
On Mon, 13 Feb 2023, Артём Яшков wrote:
> Hello again, Dormando!
> Haven't heard you for a while :)
>
> I have started updating dashb
would drop the timestamp from the output. I've not done this yet
since the watch logs don't have parity with the original debug logs.
3) most of these logs are for debugging and don't make a ton of sense to be
timed.
-Dormando
> On Dec 29, 2022, at 12:24 AM, Xuesen Liang wrote:
&
Hey,
This e-mail response serves as permission.
Policy is stated at the bottom of https://memcached.org/ and probably some
other place I forget.
Thanks for asking first!
On Mon, 26 Sep 2022, Jim St Leger wrote:
> Can someone point me to the memcached logo usage policy?
> A colleague wants to
items:36:moves_to_cold 57328
> STAT items:36:moves_to_warm 32153
> STAT items:36:moves_within_lru 68228
> STAT items:36:direct_reclaims 65140
> STAT items:36:hits_to_hot 80622
> STAT items:36:hits_to_warm 570017
> STAT items:36:hits_to_cold 27734
> STAT items:36:hits_to_temp 0
> Hello, Dormando,
>
> I'm glad you've answered!
>
> The goal is simple - it is to make memcached work properly as the server
> cashing service in our project, as it seems to me that it's not working so by
> now.
What are you specifically seeing that you disagree with
Hey,
I'm not aware of one existing yet. What java client do you currently use?
Are there any java clients with active maintainers we can contact?
On Fri, 16 Sep 2022, Javier Arias Losada wrote:
> Hi there!I love the meta protocol for memcached, and it would help
> significantly with some of
to 1.6.17? A fix just went in
fixing OOM's and excess evictions for caches with mostly large objects.
-Dormando
On Mon, 19 Sep 2022, Артём Яшков wrote:
> Hello there, I am new to using memcached, but I would like to improve the
> performance of out project by adjusting some of se
their original slab class from
the chunk size.
So now it'll use too much memory in some cases, and lowering slab chunk
max would ease that a bit... so maybe soon will finally be a good time to
lower the default chunk max a little to at least 128k or 256k.
-Dormando
On Fri, 26 Aug 2022, Hayden wrote
be nice to validate
still.
On Fri, 26 Aug 2022, dormando wrote:
> You can't build docker images or compile binaries? there's a
> docker-compose.yml in the repo already if that helps.
>
> If not I can try but I don't spend a lot of time with docker directly.
>
> On Fri, 26 Aug
til the weekend,
> and I don't have a ready way to build an updated image. Any chance you could
> create a docker image with the fix that I could grab from somewhere?
>
> On Friday, August 26, 2022 at 10:38:54 AM UTC-7 Dormando wrote:
> I have an opportunity to put this fix into a relea
Took another quick look...
Think there's an easy patch that might work:
https://github.com/memcached/memcached/pull/924
If you wouldn't mind helping validate? An external validator would help me
get it in time for the next release :)
Thanks,
-Dormando
On Wed, 24 Aug 2022, dormando wrote
large items and a relatively low memory limit, so this is why you're
seeing it so easily. I think most people setting large items have like
30G+ of memory so you end up with more spread around.
Thanks,
-Dormando
On Wed, 24 Aug 2022, Hayden wrote:
> What you're saying makes sense, and
t;end cap" memory to be found.
3) delete items as you use them so it doesn't have to evict. not the best
option.
There're code fixes I can try but I need to see what the exact symptom is
first, which is why I ask for the stats stuff.
On Wed, 24 Aug 2022, dormando wrote:
> Hey,
>
&
ose fixes may have caused too much memory to be moved away from a slab
class sometimes.
Feel free to open an issue on github to track this if you'd like.
have fun,
-Dormando
On Wed, 24 Aug 2022, Hayden wrote:
> Hello,
> I'm trying to use memcached for a use case I don't think is outlandish,
mple' work for more folks :)
Thanks,
-Dormando
--
---
You received this message because you are subscribed to the Google Groups
"memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to memcached+unsubscr...@googlegroups.com.
To view this discuss
Hey,
Definitely not enough information from what you provide here. Typically
"CPU usage goes up" isn't correlated to "memcached is slow". You usually
see CPU usage go down, because the servers are waiting on data over the
network and are thus idle.
This can change in a few ways, ie; if your PHP
> than with our current setup.
>
> This is why I was asking about the option for creating some kind of snapshot
> from a live node... or try to
> leverage the WarmRestarts to increase our efficiency.
>
> Not sure if this would bring more ideas... but I hope our use case is now
&g
Hey,
Unfortuantely I don't think it works that way. Warm restart is useful for
upgrading or slightly changing the configuration of an independent cache
node without losing the data.
However since you're expanding and contracting a cluster, keys get
remapped inbetween hosts. If you're saving the
be trivial to build and use and perform well.
Plus fancy future features as development continues.
have fun,
-Dormando
--
---
You received this message because you are subscribed to the Google Groups
"memcached" group.
To unsubscribe from this group and stop receiving emails fro
Hey,
Sorry for the late response; I have no idea who this person is or how it's
being built and there doesn't seem like a code patch?
So you should file an issue with them if you haven't already.
On Wed, 8 Dec 2021, Damian Chapman wrote:
> Hi Dormando,
> Thanks for responding to me.
>
Where did you get a windows build of 1.6.12?
We don't officially support windows, and I hadn't heard of anyone even making
recent builds of a windows fork. You're best off asking whomever's doing that
build.
> On Dec 8, 2021, at 8:17 AM, Damian Chapman wrote:
>
> It looks like Crtl-C is
personally maintain any clusters right now, so I want to be sure
to hear from folks who develop for and support clusters. Get your devs
involved as well, these features go well beyond operational support!
Thanks,
-Dormando
--
---
You received this message because you are subscribed
Hey,
Thought I had a specific FAQ page for this but maybe not?
The reason why memcached can't delete groups of keys atomically, is
because it's a distributed system by default and the servers don't
communicate. Keys are spread across many servers. You can use namespacing
instead:
Hey,
I'm not going to fix this one I think; testapp needs to be built without
NDEBUG. You shouldn't be passing that flag in; the build system makes the
main memcached binary with NDEBUG already.
On Wed, 23 Jun 2021, 張俊芝 wrote:
>
> Version: 1.6.9
>
> Steps to reproduce the bug:
>
> Run the
github.com/memcached/memcached/issues/796 - Been working on an embedded
memcached proxy. An OSS/community replacement for mcrouter/similar. If
this is interesting to you, please take an early look and help me work out
a clean route API for it!
-Dormando
--
---
You received this message
essage in the above link, but I am still confused
> about why memory limitation affect Memcached's usage. Could you give a more
> detailed explanation? If I have to give limited memory, is there a way to
> avoid this issue?
> Thank you very much for helping!
>
> Best,
> Qingchen
try '-o no_lru_crawler' ? That definitely works.
I don't know what you're doing since no code has been provided. The locks
around managing LRU tails is pretty strict; so make sure you are actually
using them correctly.
The LRU crawler works by injecting a fake item into the LRU, then using
that
recent development branches. I don't typically update
> master/next
> on there.
>
> If your co is able to sponsor development that can speed things up too.
>
> -Dormando
>
> On Tue, 6 Apr 2021, Eric Zhang wrote:
>
> > This month or next
Hey,
There are user commands which can optionally control the slab rebalancer,
so the lock is mostly for that interaction from worker threads. The
restart system also needs to stop the thread gracefully.
On Fri, 7 May 2021, Wenxin Zheng wrote:
> It seems that in 'slabs.c', slab_rebalance_thread
y
> hard to debug. Is there a way to print to stdout?
>
> Thank you very much!
> QD
>
> Sent from my iPhone
>
> > On Apr 28, 2021, at 10:33 PM, dormando wrote:
> >
> > How're you loading the data?
> >
> > From the stats it looks like you're probably ov
How're you loading the data?
>From the stats it looks like you're probably overwriting the same values
over and over (high total_items but low curr_items and no get_expired)
On Wed, 28 Apr 2021, Qingchen Dang wrote:
> Hi,
> I am trying to test my optimization of Memcached eviction, but it seems
typically update master/next
on there.
If your co is able to sponsor development that can speed things up too.
-Dormando
On Tue, 6 Apr 2021, Eric Zhang wrote:
> This month or next month is OK for me, and I will be the first one to test
> it. I can make some patches to make it
> work, based
not make it crash or
reboot safe. There is still a memory segment that needs to be saved to
survive reboots.
-Dormando
On Tue, 6 Apr 2021, Shihu Zhang wrote:
> Our program have test the feature of WarmStart which is useful. Data
> cached in Memcached is nearly never
> modified an
is by ensuring multiple requests are
pipelined at once, and there are a reasonable number of worker threads
(not more than one per CPU). If you see anything odd or have quetions
please bring up specifics, share server settings, etc.
> Thanks
> Kireet
>
>
> -Dormando
>
&
actually scales pretty well. Linearly for reads vs the number
of worker threads at tens of millions of requests per second on large
machines. What probems are you running into?
-Dormando
On Fri, 26 Mar 2021, kmr wrote:
> We are trying to experiment with using UDP vs TCP for gets to see what k
Hey,
Sorry for the delay: I grant permission for you to use the logo in your
blog post. Please link the blog post here when posted!
Thanks,
-Dormando
On Tue, 23 Mar 2021, Atsushi Sato wrote:
> To whom it may concern,
>
> Let me check again.
> We would like to use the memcached logo
Hey,
Memcached only "thinks" in binary blobs. Append is just stacking the
new object at the end of the new object. If whatever you use to serialize
and de-serialize your objects doesn't understand this it won't return all
of the objects.
You'll need to modify the java client or otherwise provide
nope! sorry
On Fri, 1 Jan 2021, Erjan G. wrote:
> do u have it available or plan to do it?
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "memcached" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
is available, so we’ll probably plan to migrate.
>
> Adjusting growth factor makes sense. I did a quick google and don’t see
> any definitive formula to calculate an appropriate number. I’ll probably
> start with 2 or 3 and adjust it from there.
>
> Thanks,
>
> Tony Wu
>
&g
1.5.what?
also yes, chunk_size_growth_factor. don't set it to 1.02. set it to
something so your slab classes are more evenly distributed. the max is 63.
On Thu, 12 Nov 2020, Tony Wu wrote:
> Hi Dormando,
>
> Thanks for the reply, I believe the engine version is 1.5. By multiplier
&g
What version are they running now? That stat output looks pretty sparse.
Unfortunately when it comes to elasticache the answer is probably to just
beg them to upgrade to a newer version. they tend to run really old and
newer verisons do a lot better at balancing memory.
This is also suspect:
>
ignore this, unless you feel like there's a significant
memory waste going on. You can change the slab growth factor (-f) to
create more classes in the lower numbers than higher numbers but again I
wouldn't bother unless you really need to.
It doesn't "simplify" the logic either way.
-Dorma
Hey,
I'm the right person to talk to here. You can e-mail me privately
(dormando [at] rydia dot net).
Just need the new logo + when to update it. Easy enough.
have fun,
-Dormando
On Wed, 16 Sep 2020, Kyle Gannon wrote:
> Hello,
>
> Hope all is well!
>
> My name is Kyle an
Hey,
Sorry for the super late reply.
I'm tracking a fix for this here:
https://github.com/memcached/memcached/issues/541 - but not entirely sure
when I'll get to it. It's not easy to avoid but should be relatively rare.
It happens when the system thinks it has enough memory free to move a
page,
Thanks,
I'll allow this for a one-time use.
Thanks,
-Dormando
On Tue, 14 Jul 2020, Kiran Patil wrote:
>
>
> Hi Dormondo.
>
>
> Sorry I was not able to spend time on that patch due to internal priority
> change and my focus got shifted meanwhile.
>
>
> Now we
Hey,
I think we never got that patch merged? I'd love to allow this but I'm
worried people might get confused since it's not something you can do with
the released version of memcached?
Thanks,
-Dormando
On Thu, 9 Jul 2020, Kiran Patil wrote:
>
> Hello Dormando,
>
>
>
>
I guess that's fair.
On Wed, 8 Jul 2020, Nicolas Motte wrote:
> Thx Dormando!
> I ll then use this rule for the time being:
>
> - 1.4 is dead
> - 1.5 is still supported (in the sense that a major security issue could be
> fixed)
> - 1.6 is the preferred version
>
>
Hey,
In extreme cases we would provide patches, and there's nothing stopping me
from releasing a new 1.5 version. Most distro's just patch what versions
they maintain, which is a wide swath of them.
The only difference between later 1.4 and early 1.5 versions were the
defaults enabled, so
o do was turn on automove, but I don't have your
stats from when you did have evictions so I can't say for sure.
> >If it were full and automove was off like it is now, you would see
> problems over time. Noted.Thank you for the input. :)
>
> Thank you,
> Shweta
>
> On Wednesd
Wednesday, July 8, 2020 at 9:35:19 AM UTC+5:30, Dormando wrote:
> Oh, so this is amazon elasticache?
>
> On Tue, 7 Jul 2020, Shweta Agrawal wrote:
>
> > We use aws for deployment and don't have that information. What
> particularly looks odd in settings?
>
Oh, so this is amazon elasticache?
On Tue, 7 Jul 2020, Shweta Agrawal wrote:
> We use aws for deployment and don't have that information. What particularly
> looks odd in settings?
>
> On Wednesday, July 8, 2020 at 8:10:04 AM UTC+5:30, Dormando wrote:
> what're your
what're your start arguments? the settings look a little odd. ie; the full
commandline (censoring anything important) that you used to start
memcached
On Tue, 7 Jul 2020, Shweta Agrawal wrote:
> Sorry. Here it is.
>
> On Wednesday, July 8, 2020 at 12:38:38 AM UTC+5:30, Dorma
'stats settings' file is empty
On Tue, 7 Jul 2020, Shweta Agrawal wrote:
> Hi Dormando,
> Got the stats for production. Please find attached files for stats settings.
> stats items, stats, stats slabs. Summary for all slabs.
>
> Other details that might help:
> * TTL i
takes to read the data
from the network is so large that we can afford to do extra processing.
> 3Mb_items_eviction.png
>
>
> Thank you,
> Shweta
>
>
> On Sunday, July 5, 2020 at 1:13:19 AM UTC+5:30, Dormando wrote:
> (memory_requested / (chunk_size * chunk_used)) * 1
ich has calculations for the same. The script is from
> memcahe repo with additional calculation for efficiency.
> Will it be possible for you to verify if the efficiency calculation is
> correct?
>
> Thank you,
> Shweta
>
> On Saturday, July 4, 2020 at 1:08:23 PM UTC+5:30, Dorm
ah okay.
I'll need the raw output from "stats items" and "stats slabs". I don't
think that efficiency column is very helpful.
On Fri, 3 Jul 2020, Shweta Agrawal wrote:
>
>
> On Saturday, July 4, 2020 at 9:41:49 AM UTC+5:30, Dormando wrote:
> No attachm
t; data length / etc.
>
> We have much less data than 39 GB. As after facing evictions, it has been
> always kept higher than expected data-size.
> TTL is two days or more.
> From my observation items size(data-length) is in the range of 300Bytes to
> 500K after compression.
>
of data and your expecations are a bit off. This will also depending on
the TTL's you're setting and how often/quickly your items change size.
Also things like your serialization method / compression / key length vs
data length / etc.
-Dormando
> On Saturday, July 4, 2020 at 12:23:09 AM UTC+5:3
Hey,
Looks like I never updated the manpage. In the past the item size max was
achieved by changing the slab page size, but that hasn't been true for a
long time.
>From ./memcached -h:
-m, --memory-limit= item memory in megabytes (default: 64)
... -m just means the memory limit in megabytes,
Hey,
The "cfd" is the client FD, which you can resolve via "stats conns".
We could add more information. I need to rethink this a bit, maybe.
On Sun, 21 Jun 2020, chinmay gupta wrote:
> Hey
>
> Would it be possible to add client IP information to the `watch ...` command
> log response with
Hey,
Guess I don't mail here much anymore :) Kind of unsure what audience is
left to be honest. In case there is:
Prototype partially written allocation-free memcached C client:
https://github.com/dormando/mcmc (and dev issue:
https://github.com/dormando/mcmc/issues/1) - working to nail down
Absolutely. That's exactly the workflow it's designed for, we just haven't
updated any of the systemd scripts to be more friendly for it.
Also a caveat; there _was_ a bug fixed relatively recently with the
restart code. I don't know if ubuntu backports these. If you use large
objects (> 512k)
some community/chat/something for some systems
admnistration help to get this going. Sounds like you're a bit over your
head :(
good luck,
-Dormando
On Wed, 10 Jun 2020, Even Onsager wrote:
> My site runs on one webserver and we rely heavily on memcached to make it
> snappy, to the
on that particular node you ran the stats command on.
On Fri, 29 May 2020, Gautam Worah wrote:
> Is the max_connections variable representative of the maximum number of
> client connections possible per node or for the entire cluster?
>
> Command used: STAT max_connections
>
> --
>
> ---
> You
Hey,
I can probably help if you contact me privately. If it's something you can
get help with publicly go ahead and detail what's going on :)
have fun,
-Dormando
On Tue, 26 May 2020, 'Dan' via memcached wrote:
> Hi,
> We are a UK-based travel site looking for some help/checking
It says it can't write the pid file, so it's probably failing to start
there.
Try starting it manually with those options and fix it until it works?
On Mon, 11 May 2020, Alexander wrote:
> I tried with and without UFW (disabled/enabled), I ran /etc/init.d/memcached
> status:
> ●
Hey,
I hear you, I have no idea what's generating that message. it's not part
of memcached. What is generating it? How did you install memcached into
your system?
On Sat, 9 May 2020, Pablo C wrote:
> I am asking cause I have don't know much about memcached.
> I checked and it seem to be running
What is generating that message? I have no idea what that means :(
It sounds like it's using too much CPU? But it's not killing it, so you'll
just keep getting this warning every hour?
How did you install memcached?
On Sat, 9 May 2020, Pablo C wrote:
>
> We have a installed memcached a few
> Martin
>
> On Tue, Apr 7, 2020 at 3:29 PM Martin Grigorov
> wrote:
> Hi Dormando,
>
> This is a continuation of the mail thread with subject "Is ARM64
> officially supported ?" [1]
>
> I've refreshed my Perl coding skills and came up with this wrappe
discuss.
-Dormando
On Mon, 9 Mar 2020, Martin Grigorov wrote:
> Hi Dormando,
>
> On Mon, Mar 9, 2020 at 9:19 AM Martin Grigorov
> wrote:
> Hi Dormando,
>
> On Fri, Mar 6, 2020 at 10:15 PM dormando wrote:
> Yo,
>
> Just to add in: yes we support ARM64.
Sorry, there's no support for repcached.
On Wed, 15 Apr 2020, pratibha sharma Jagnere wrote:
> Hi,
> has anyone used repcached package recently.
> I am trying to setup but when I run the memcached service, I am getting
> segmentation fault.
>
> Is there any other alternative?
>
> --
>
> ---
>
Bit late in responding:
That wiki page is about the older DDoS. Not about a DoS. They're
completely different. This bug is more simply a server crash, not
convincing the server to do stupid shit.
I'm not going to write tests for it, but someone else is free to.
On Thu, 2 Apr 2020, Victor
Hey,
https://github.com/memcached/memcached/blob/master/doc/protocol.txt#L176
there is a no-dependency authentication system for the text protocol.
On Thu, 9 Apr 2020, Sambasivarao Gajula wrote:
> Hello Memcached community,
> Do we have in-service authentication felicity in the memcached
I haven't at all looked at what
you've done) is to break down the changes into small chunks to be
individually reviewed and upstreamed so that the fork simply shrinks with
time. There should be some changes that're easier than others to upstream.
thanks,
-Dormando
On Sat, 4 Apr 2020, Jefty
If you're still stuck I'll write more of a guide, just let me know.
On Sun, 22 Mar 2020, dormando wrote:
> Hey,
>
> I thought I wrote this in the rest of the e-mail + the README: it doesn't
> print stats at the end. you run the benchmark and then pull stats via
> other utilitie
u, Mar 19, 2020 at 9:06 PM dormando wrote:
> memtier is trash. Check the README for mc-crusher, I just updated it a
> bit
> a day or two ago. Those numbers are incredibly low, I'd have to dig a
> laptop out of the 90's to get something to perform that badly.
>
ase
> tsc_adjust
> bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx avx512f avx512dq rdseed adx smap
> clflushopt clwb avx512cd avx512bw avx512vl xsaveopt xsavec xgetbv1 arat
> avx512_vnni md_clear flush_l1d arch_capabilities
>
> Both with 16GB RAM.
>
>
> Regards,
> Martin
>
on't know how to check SessionID in
> Memcached.
> Do you have any related commands?
>
> 2020년 3월 10일 화요일 오전 4시 8분 13초 UTC+9, Dormando 님의 말:
> Hey,
>
> I'm not completely sure on what you're trying to do, but there's the
> `watch` command (see doc/protoco
Hey,
I'm not completely sure on what you're trying to do, but there's the
`watch` command (see doc/protocol.txt). It's missing a log of log points
still but acts similar to redis monitor. Clients are identified by their
file descriptor, not any sort of unique session id.
On Mon, 9 Mar 2020, 김상철
Hey,
So first part: https://github.com/memcached/memcached/wiki/ReleaseNotes160
We won't be adding further features to the binary protocol, instead
extending off of the new text based meta protocol. I'll be looking at
your proposal more closely in a week or so now that 1.6.0 is out.
-Dormando
https://github.com/memcached/memcached/wiki/ReleaseNotes160
enjoy
--
---
You received this message because you are subscribed to the Google Groups
"memcached" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to memcached+unsubscr...@googlegroups.com.
To
Added a blurb on the hardware page:
https://github.com/memcached/memcached/wiki/Hardware
On Sun, 8 Mar 2020, Emilio Fernandes wrote:
> Hola Dormando!
> Thank you for confirming that ARM64 is officially supported!
> Do you think it would be a good idea to mention the list of the
M64 platforms,
I just can't do any specific perf work unless someone donates hardware.
-Dormando
On Fri, 6 Mar 2020, Martin Grigorov wrote:
> Hi Emilio,
>
> On Fri, Mar 6, 2020 at 9:14 AM Emilio Fernandes
> wrote:
> Thank you for sharing your experience, Martin!
> I'v
Thanks for getting this started!
It may take a while for me to review/think it over. I've been planning on
tackling this but have a lot of research to do.
On Thu, 27 Feb 2020, 'Iqram Mahmud' via memcached wrote:
> Hi Dormando and memcached community,
>
> I work in Google Cloud Platfo
https://github.com/memcached/memcached/pull/592
I don't have a mac. looking for someone to give it a look over so I can
finally merge it :)
--
---
You received this message because you are subscribed to the Google Groups
"memcached" group.
To unsubscribe from this group and stop receiving
than a
hundred milliseconds or per page.
-Dormando
On Mon, 10 Feb 2020, 'theonajim' via memcached wrote:
> For extstore feature, are there guidelines on size to allocate for extstore
> file? For example, if the drive has 500 GB capacity, do we allocate all 500
> GB, 250 GB (50%) or
&g
https://github.com/memcached/memcached/wiki/ReleaseNotes1522
fixes a segfault introduced in 1.5.20. In case anyone now or in the future
finds a segfault in 1.5.20 or .21 :)
-Dormando
--
---
You received this message because you are subscribed to the Google Groups
"memcached&q
l machine, while I have the same Memcached configuration for
> both machines. I have attached the numbers for the two machines.
>
> Thanks,
> Alireza
>
> On Sun, Dec 15, 2019 at 3:40 PM dormando wrote:
> What're you trying to accomplish?
>
> Can you include th
> showing userspace time spent for each worker. Apparently worker thread number
> 1,2,4 and 5 have spent more time in userspace, so I'm concluding here that
> 1,2,4 and 5 are my actual worker threads, and worker 3 and 6 are just internal
> worker threads of Memcached. Doe
ads. Older versions have some of these threads, but
they were not enabled by default until 1.5.0.
-Dormando
On Sat, 14 Dec 2019, Alireza Sanaee wrote:
> Hello,
> I'm running Memcached on two different machines with different
> specifications. And I specify the number of worker t
1 - 100 of 993 matches
Mail list logo
