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

Jump to bottom

Create Segment w/ Page URL filter (Huge Database) #4509

Closed
anonymous-matomo-user opened this issue Jan 13, 2014 · 3 comments
Closed

Create Segment w/ Page URL filter (Huge Database) #4509

anonymous-matomo-user opened this issue Jan 13, 2014 · 3 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. duplicate For issues that already existed in our issue tracker and were reported previously. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Milestone
Long term

Comments

@anonymous-matomo-user
Copy link

Running v2.0.2
Database is approx 10gb.
When I go to create a new segment using the page url filter, it takes an incredibly long time to pre-fill the url list (Avg 5-10mins), effectively locking the table, resulting in locked transactions for the live stats data that is coming in. We're getting on average 5 hit per second during peak times. We don't want to go over 500 max connections on our database, which we max every time i try to add a new segment. Is there a way to not have the segment editor query the table for the prefilled url list so i can just specify the url i want to use? Thanks!
Keywords: Segment Editor Large Database
@gaumondp
Copy link

Related to #4253

Skerbater, do you agree that a new preference like "no ajax query in segment editor" would do the trick?

Dali

@anonymous-matomo-user
Copy link
Author

Agreed... or remove it completely. Typically people already know what url value is that they want to segment. It's no problem when working with small data, but we are huge and continue to grow, so this is a problem.

@mattab
Copy link
Member

mattab commented Feb 6, 2014

See #4253

@anonymous-matomo-user anonymous-matomo-user added this to the 2.x - The Great Piwik 2.x Backlog milestone Jul 8, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Bug For errors / faults / flaws / inconsistencies etc. duplicate For issues that already existed in our issue tracker and were reported previously. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical.
Projects
None yet
Milestone
Long term
Development

No branches or pull requests
3 participants
@mattab @gaumondp @anonymous-matomo-user