GitHub user sebbASF opened an issue:
Issues with scaling; inefficient use of client resources
The backend database should not have any problems with handling very large
numbers of mailing lists and mails in each list.
However the scripts that interface with the database mostly assume that it
is OK to return data from all lists or all mails (at least up to a certain
GUI, this means that the browser can be presented with very large datasets,
requiring a lot of network traffic. This can impact browser memory requirements
and potentially broadband date usage. It certainly impacts mobile data usage.
Much of the data that is returned by the scripts is not needed immediately,
and may never be used.
Whilst this does reduce lag, it is wasteful of client resources
For example, the initial display only shows domain names, yet the code has
used both preferences.lua and pminfo.lua both of which return data about all
lists as well as all domains.
Again, once a mailing list is selected, the entire thread structure (with a
limit of 15k) for the current period is downloaded by stats.lua, even though
only a few mails can be displayed at a time.
Also preferences.lua and pminfo.lua return some overlapping data
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket