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

Test piwik on a 50,000+ visits per day website #5457

Closed
mattab opened this issue Jan 3, 2008 · 1 comment
Closed

Test piwik on a 50,000+ visits per day website #5457

mattab opened this issue Jan 3, 2008 · 1 comment
Labels
Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Jan 3, 2008

This test is very important as it will lead to necessary changes and optimization in
1. the DB design (index optimization, fields types)
2. the logging engine (how it behaves under heavy load, how the statistics logging can be optimized)
3. the archiving process (memory usage, saving computation time)
4. the interface (the DataTable scalable?)

This test will require to add new features such as
- [Add possibility to limit the number of rows saved in the datatable during the archiving](ticket:36)

@mattab
Copy link
Member Author

mattab commented Oct 10, 2008

should not be a ticket. will create a new consolidated “performance improvement” task

@mattab mattab added this to the Piwik 0.9.9 - Stable release milestone Jul 8, 2014
@mattab mattab added the wontfix label Aug 3, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. Task Indicates an issue is neither a feature nor a bug and it's purely a "technical" change. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Projects
None yet
Development

No branches or pull requests

1 participant