https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11998 --- Comment #121 from Jacek Ablewicz <abl@biblos.pk.edu.pl> --- (In reply to Jonathan Druart from comment #120)

(In reply to Jonathan Druart from comment #119)

...

Actually it's certainly caused by the circular dependency.

Koha::Cache::_initialize_fastmmap could read the config file instead of calling C4::Context->config.

IMO delaying cache init / moving Koha::Cache->get_instance() call into preference() sub may be a better idea. Especially as in current master C4::Context::read_config_file() is apparently called 2+ times per script run allready: - 1st time when we do 'use Koha::Context;' anywhere - 2nd time when we intialize the database connection in Koha::Database via schema() / _new_schema() sub :)

But the question is: Does someone use fasmmap?

Probably not (but thats the only shared / permanent caching system available apart from memcache - which has its own quirks and constraints). I only encountered this problem because I was curious how would the 3 different caching systems compare performance-wise, since we are going to use them for something so much speed-sensitive (i.e preference fetching). -- You are receiving this mail because: You are watching all bug changes.