Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory and performance problem with big (>30,000+ pubs) Aigaion database #10

Open
kristiank opened this issue Mar 21, 2013 · 0 comments

Comments

@kristiank
Copy link

Aigaion keeps every publication's pub_id and bibtex_id stored in a session cache variable for later crossreferencing needs (helpers/bibtex.php). Instead of keeping everything in a cached variable, it would be better to use database queries.

For memory it would be better, because the bigger your database is, the more memory it will require (and reach PHP's memory_limit, by default 128 MiB).

For performance it would be much better, because there would be no need for looping through all the tens of thousands of publication rows stored in Aigaion (nor to send this data between MySQL and PHP) every time any single publication is added/updated/deleted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant