Roundup Tracker - Issues

Issue 2550721

Support for memcached
Type: resource usage Severity: normal
Components: Database Versions: 1.4
Status: new
: : ber, rodriguealcazar, rouilj
Priority: : patch

Created on 2011-08-19 16:13 by rodriguealcazar, last changed 2022-08-09 01:34 by rouilj.

File name Uploaded Description Edit Remove
memcache_support.diff rodriguealcazar, 2011-08-19 16:13 patch to support integration with memcached
msg4384 Author: [hidden] (rodriguealcazar) Date: 2011-08-19 16:13
This is a patch that makes it possible to use memcached instead of the
in-memory database cache.

With the patch applied, you simply need to add a config param:

memcache = localhost:11211

Hope this can be useful.
msg4387 Author: [hidden] (ber) Date: 2011-08-22 08:13
Hi Rodrigue,
thanks for the contribution! It is well appreciate.
I saw that you have also written unit-tests! Very nice!

Now the next step is that we find someone that can test the patch.
Can you write a few sentences about the advantages that
we could possibly include in the news or can be used for testing
so that the improvements can be felt. We want to give users an idea
how they profit from your addition.
Also an entry to changes would be intesting.

Best Regards,
msg4394 Author: [hidden] (rodriguealcazar) Date: 2011-08-24 10:06
Hi Bernhard,

> Can you write a few sentences about the advantages

this patch is purely a performance improvement. Memcached has improved
the responsiveness of our install of roundup. As for figures, I should
be able to take a few moments to time some roundup requests with and
without memcached enabled and get a better sense of what the performance
gain is.

Note that by default, the patch does not change the current roundup

> Also an entry to changes would be intesting.

I'm not sure what you mean here?

msg4395 Author: [hidden] (ber) Date: 2011-08-24 10:15
with changes I've referred to
It makes the life of the maintainers easier, if patches already
contain some documentation or a changes entry.

Like with your patch it would be cool to know for the documentation.
what people could do to activate the benefits or migrate from
old settings.

If this is a general improvement should it be a default for new tracker
msg4396 Author: [hidden] (rodriguealcazar) Date: 2011-08-24 10:19
Got it. I will update the changes.txt as well then.

> If this is a general improvement should it be a default for new tracker

Well, that would add a dependency on memcached and force users to
install it along with roundup, so I would say that it should not be a
default for new trackers.
msg5605 Author: [hidden] (rouilj) Date: 2016-06-18 03:09
Rodrigue have you by change updated this patch to a more current
release of roundup?

I tried applying the patch and unsurprisingly the patch doesn't apply
to the current version since it's been 4-5 years.

I have managed to hand apply it, but there are some sections thathave
changed significantly.

Also did you consider replacing the cache in back_anydm as you have
with rdbms_common?
msg7254 Author: [hidden] (rouilj) Date: 2021-05-28 01:59

Are you still around? If so I would like to work with you on getting
this patch installed on a recent version.

Also I was wondering if you had thought of using this as an
option for the session database. I have had performance issues
when using the session db and memcached (or redis) should solve
that issue.
msg7633 Author: [hidden] (rouilj) Date: 2022-08-09 01:34
Article on memcached that includes a method to safely update an element in the cache.

Not sure if it applies in this use case but...
Date User Action Args
2022-08-09 01:34:59rouiljsetmessages: + msg7633
2021-05-28 01:59:05rouiljsetmessages: + msg7254
2016-06-18 03:09:03rouiljsetnosy: + rouilj
messages: + msg5605
2011-08-24 10:19:17rodriguealcazarsetmessages: + msg4396
2011-08-24 10:15:58bersetmessages: + msg4395
2011-08-24 10:06:58rodriguealcazarsetmessages: + msg4394
2011-08-22 08:13:23bersetnosy: + ber
messages: + msg4387
2011-08-19 16:13:09rodriguealcazarcreate