Replace usage of interactions table on admin page #1339
Comments
|
I believe the only graphs that use the
@jonfroehlich how important do you think each of these graphs are for the admin page? I see 2 reasonable options for dealing with these graphs:
A third option could be figuring out a new way of computing "time spent" that is less precise, but doesn't require looking at interaction logs, and is thus much faster to compute. This would have the advantage of updating in real-time instead of nightly. But for these particular graphs, I don't think we need the most up to date data, so it isn't worth the time to implement. |
|
@jonfroehlich do you need those two graphs on the admin page? |
|
No. Not at the moment at least. Sorry i missed your post on Friday
…Sent from my iPhone
On Jan 22, 2019, at 10:35 AM, Mikey Saugstad ***@***.***> wrote:
@jonfroehlich do you need those two graphs on the admin page?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
No problem. I'll just remove them from the admin page for now then to speed up the page load. Shall I port that change over to the frozen DC code as well once I've written it? |
|
I don't think it's necessary to port over, unless you do?
…On Tue, Jan 22, 2019 at 11:35 AM Mikey Saugstad ***@***.***> wrote:
No problem. I'll just remove them from the admin page for now then to
speed up the page load. Shall I port that change over to the frozen DC code
as well once I've written it?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1339 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABi-9R5dx_pENcVBUOO1NwmzVYGqptaKks5vF2fjgaJpZM4Ycw3K>
.
--
Jon Froehlich
Associate Professor
Paul G. Allen School of Computer Science & Engineering
University of Washington
http://www.cs.umd.edu/~jonf/
http://makeabilitylab.io
@jonfroehlich <https://twitter.com/jonfroehlich> - Twitter
|
|
Only if you plan on using the admin dashboard's analytics page on that server. So probably not necessary. |
|
I don't think so. Any stats we'll run on that data will be run offline like
you did for CHI'19.
Jon
…On Tue, Jan 22, 2019 at 11:40 AM Mikey Saugstad ***@***.***> wrote:
Only if you plan on using the admin dashboard's analytics page on that
server. So probably not necessary.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1339 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABi-9QK8ilxvxE2hj0MxUvLpKuYx_hwHks5vF2k7gaJpZM4Ycw3K>
.
--
Jon Froehlich
Associate Professor
Paul G. Allen School of Computer Science & Engineering
University of Washington
http://www.cs.umd.edu/~jonf/
http://makeabilitylab.io
@jonfroehlich <https://twitter.com/jonfroehlich> - Twitter
|
ghost
added
the
|
Closing via #1401 |
Although PR #1325 will improve the initial load time of the admin page significantly (to under 30 seconds), loading the analytics tab still takes several minutes, and it even fails due to the JVM running out of heap space. The reason is that we are trying to run queries on the
audit_task_interactiontable.As discussed in a meeting today, this table should really only be used for data analysis purposes; we shouldn't be trying to access it on any part of the website (except to insert new interactions). So we need to put anything we truly want to access into separate tables that can be queried quickly, and remove any other accesses to this table that are not necessary so that we can view our admin dashboard in a timely manner :)
The text was updated successfully, but these errors were encountered: