I have a 91mb /opt/graphite/storage/index file and the UI's suck to load

Asked by Gary Richardson on 2012-04-24

I recently upgraded to 0.9.9 and I've run into a problem:

[root@ip-10-127-155-193 storage]# wc -l index
1346368 index
[root@ip-10-127-155-193 storage]# ls -lha index
-rw-r--r-- 1 apache apache 91M Apr 24 14:17 index

which is accurate.. I have many small and sparse graphs. I don't think it's necessarily a 0.9.9 problem, but I don't seem to remember the index file in 0.9.8.

When I try to expand the 'Graphite' tree in the old UI, it typically times out. Using the new dashboard causes apache to grind the server to a halt. I'm guessing it's trying to search through the file.

I realize I'm probably not in the norm for usage, but is there anything I can do to improve the performance of the web UI?

Thanks!

Question information

Language:
English Edit question
Status:
Answered
For:
Graphite Edit question
Assignee:
No assignee Edit question
Last query:
2012-04-24
Last reply:
2012-11-01
Michael Leinartas (mleinartas) said : #1

The index is only used for search functionality (not for auto-complete or anything like that). You may want to just zero out the file if you can live without search - once the file is present it's not recreated automatically.

This search 'solution' will hopefully be gutted for something more robust and better scaling in a future release

Nicholas Leskiw (nleskiw) said : #2

The index file replaces the old behavior of reading the directory tree from disk. So theoretically it should be faster than the old method in 0.9.8.

Cody Stevens (cody-stevens) said : #3

Enabling the WSGIImportScript directive to load the indexes before any requests are handled seems to have fixed the issue for me in 0.9.10. It is documented in the graphite.wsgi.example file but the directive is typo'ed.

Can you help with this problem?

Provide an answer of your own, or ask Gary Richardson for more information if necessary.

To post a message you must log in.