Editing Twitter Analysis DB Details
Jump to navigation
Jump to search
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 9: | Line 9: | ||
* I currently run the db on a ram disk, in any case put on your fastest drive. | * I currently run the db on a ram disk, in any case put on your fastest drive. | ||
− | * I have not tuned the db for performance. Got suggestions ( that are more than just guesses ) | + | * I have not tuned the db for performance. Got suggestions ( that are more than just guesses ). I am sure that more indexing might help, will try in time. |
* Code is not optimized either. For most of it this does not matter. Looks like DB performance is the main restriction. Not an issue for me now. | * Code is not optimized either. For most of it this does not matter. Looks like DB performance is the main restriction. Not an issue for me now. |