APCu storage and shared memory

Hello @freshuk !

Thanks for your interest in DecaLog and sorry for the empty “consoles” menu. It’s a mistake on my side: this menu should not be visible if you don’t have shared memory enabled on your server. Basically, shared memory is needed by the consoles to work… This empty menu will not cause any issue, but I must admit it is not fine to have it. My apologies, it will be fixed in the next release.

On its side, APCu is a fast way to store things in memory without the need for a database. If you use DecaLog internal viewers (for events or for traces) and if you have APCu enabled on your server, you can use it as storage mechanism (when creating a logger) instead of database. It will speedup things. But it’s not mandatory.

If you have access to your server config, you can activate APCu and shared memory as follow :

APCu: https://www.php.net/manual/en/book.apcu.php
Shared memory: https://www.php.net/manual/en/book.shmop.php

But, once again, this is not a requirement for DecaLog to work ??

Thank you for the prompt answer and top class plugin!
No issue for the empty menu, just wanted to make sure its not something on my side.
As for APCu, is it faster than redis object cache?

Hey, thanks for your kind words <3

APCu is much more faster than other object cache as it is pure in-memory object cache. But it is not stored elsewhere than in the server memory. So, it’s not “server-reboot” tolerant… You restart your server === you flush your cache ??