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

Making features with high performance demand possible #9289

Closed
hpvd opened this issue Nov 26, 2015 · 2 comments
Closed

Making features with high performance demand possible #9289

hpvd opened this issue Nov 26, 2015 · 2 comments
Labels
answered For when a question was asked and we referred to forum or answered it.

Comments

@hpvd
Copy link

hpvd commented Nov 26, 2015

Some ideas for features would be great, but they may stress a piwik server.

This ticket is about making it possible to implement these features and giving ideas
why "performance reasons" shouldn't be a blocker.

A) Some reasons why "performance reason" it's not always a "killer" and why and how one can deal with it:

  1. piwik is very often used on pages with very low traffic

  2. one did not need all information on load of a page so one can display it when it's ready

  3. performance of server hardware is growing very fast (Multicore CPU, tons of RAM, SSD, PCIe-NVME SSDs...)

  4. Performance of software grows, e.g. PHP 5.6 => 7.0

  5. sometimes one do not need the very exact number:

  • so one can "Stop counting" after a special amount of time and show something like "1000+"
  • one can reuse numbers
  • one can preindex values (on times when there is low server load)
  1. data could often be (re-)used on several places

  2. one can implement a switch in settings to activate all things which are great but power consuming (for users with a good quotient of vistors/server power and backend user/server power)

  3. one can cut the worst case: do not show if segment is "all visits"

  4. ...

I'm no developer, but probably there are several more ideas to work with power demanding tasks in general...

This is an extract of write up #9110

B) of course not a solution but a demonstration, that others are working with perfect performance too (e.g. counting number of entries)
Yes of course it looks unfair because google has other "resources", but they also have other amounts of data to deal with ;-)

2015-11-26_06h49_38

C) Would be good to have some kind of best practise guide for working on performance relevant things within piwik.

D) Would be good to have a new label for issues of type: "performance demanding"
so every one discussing or working on this issue is aware to take care for this

E) This is a list of things which were already dropped because of not possible because of performance reasons - maybe one can revise them again

  1. Visitor log: display total number of visits in pagination at bottom of page #9110

F) This is a list of all issues where performance should be observed:

  1. Visitor log: display total number of visits in pagination at bottom of page #9110
  2. show instant feedback on period & segment selector usage (result counting) #9109
  3. New plugin: provide simple UI to invalidate old reports #8942
  4. Website loading slowly due to Piwik slow reverse DNS query  #8785
  5. Enable by default the Heart beat timer to process a more accurate time on page and visit duration #8225

Please add all your ideas and findings to A)...F)

@tsteur
Copy link
Member

tsteur commented Nov 26, 2015

BTW: There is also #6759 where we worked on some tweaks. Some of those issues might be actually not such a big deal anymore (I haven't looked at the one you mentioned yet).

@mattab
Copy link
Member

mattab commented Nov 27, 2015

Hi @hpvd I'm not sure what this issue is about, as it references other issues. if you have specific new suggestions please create one issue for each

@mattab mattab closed this as completed Nov 27, 2015
@mattab mattab added the answered For when a question was asked and we referred to forum or answered it. label Nov 27, 2015
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.
Projects
None yet
Development

No branches or pull requests

3 participants