There was a single setting my team was looking at today and wish we could have changed dynamically: the reqs_per_event setting. Right now in order to change it we need to shut down the process and start it again with a different -R parameter. I don't see a way to change many of the settings, though there are some that are ad-hoc changeable through some stats commands. I was going to see if I could patch memcached to be able to change the reqs_per_event setting at runtime, but before doing so I wanted to check to see if that's something that would be amenable. I also didn't want to do something specifically for that setting if it was going to be better to add it as a general feature.
I see some pros and cons: One easy pro is that you can easily change things at runtime to save performance while not losing all of your data. If client request patterns change, the process can react. A con is that the startup parameters won't necessarily match what the process is doing, so they are no longer going to be a useful way to determine the settings of memcached. Instead you would need to connect and issue a stats settings command to read them. It also introduces change in places that may have previously never seen it, e.g. the reqs_per_event setting is simply read at the beginning of the drive_machine loop. It might need some kind of synchronization around it now instead. I don't think it necessarily needs it on x86_64 but it might on other platforms which I am not familiar with. -- --- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
