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

Keep Performance- and storage-demand ok when using extensive event tracking #5347

Closed
hpvd opened this issue Jun 15, 2014 · 6 comments
Closed
Labels
answered For when a question was asked and we referred to forum or answered it. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.

Comments

@hpvd
Copy link

hpvd commented Jun 15, 2014

Since event tracking is available, this great new feature could easily blow up the total number of "things" being tracked within each visit.

E.g. if having implemented the possibility to track 5 events on each site and each visitor "uses" (->trigger) only 2 of them in average

-> you got instead of 1 site visit 3 "things" to track (Factor 3)
But this number could easily raise to factor 5 or even more...

The goal of is ticket is to collect ideas to prevent a huge impact on

  1. Performance and
  2. Storage space
@hpvd
Copy link
Author

hpvd commented Jun 15, 2014

for the performance there are at least 3 field to have a look on:
a) during tracking
b) during archiving
c) during data analyses
since I'm no programmer, probably there are some more...

@mattab
Copy link
Member

mattab commented Jun 20, 2014

do you mind posting this idea in this related ticket? #5364

@mattab
Copy link
Member

mattab commented Jun 20, 2014

I just understand now your question. So the answer is: consider "events" exactly the same as a "page view" as basically, it brings approximately the same complexity.

@hpvd
Copy link
Author

hpvd commented Jun 20, 2014

sorry this ticket is about something different than #5364
=> reopened it.

The goal is to find things that could make it "easier" (less performance demanding, less storage intensive) tracking events than site visits.

One thing is that several events are often on the same site.
Maybe one could use this characteristic also for performance- and storage- demand lowering,
as it is already been used for simplification the Customer log view (the url is only shown if it's a different than the parents site, see #5189 )

@mattab
Copy link
Member

mattab commented Jun 24, 2014

use this characteristic also for performance- and storage- demand lowering,

Do you think that event tracking can be more performant and/or storage efficient?

@hpvd I don't understand the scope or request in the ticket. Could you please explain what you meant?

@hpvd hpvd added this to the Future releases milestone Jul 8, 2014
@mattab mattab modified the milestones: Long term, Mid term Dec 23, 2015
@mattab mattab modified the milestones: Long term, Mid term Dec 5, 2016
@mattab
Copy link
Member

mattab commented Jun 19, 2017

see #5347 (comment)

@mattab mattab closed this as completed Jun 19, 2017
@mattab mattab added the answered For when a question was asked and we referred to forum or answered it. label Jun 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
answered For when a question was asked and we referred to forum or answered it. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Projects
None yet
Development

No branches or pull requests

2 participants