Ticket #427 (closed defect: worksforme)

Opened 5 years ago

Last modified 5 years ago

samples page in study view is slow

Reported by: work@… Owned by: robert@…
Priority: major Milestone: 0.8.4
Component: Study view Version: 0.8.0
Keywords: Cc:
Hardware: Operating system:
Product: URL:

Description

(from #416)

the samples tab in the show study page is quite slow

Change History

comment:1 Changed 5 years ago by work@…

  • Milestone changed from 0.8.1 to 0.8.2

comment:2 Changed 5 years ago by work@…

  • Status changed from new to closed
  • Resolution set to wontfix

bit of a non issue... if you have lots of data everything becomes slow (ajax, rendering, dom, etc), the consequence of using a web platform...

comment:3 Changed 5 years ago by robert@…

  • Status changed from closed to reopened
  • Resolution wontfix deleted

This is not a non-issue. The view became slow with only 500 samples, which is not uncommon nor very much for a web application.

Still needs to be solved.

comment:4 Changed 5 years ago by business@…

  • Milestone changed from 0.8.2 to 0.8.3

This issue needs more discussion.

comment:5 Changed 5 years ago by work@…

  • Component changed from Unknown to Study view

comment:6 Changed 5 years ago by work@…

Use the Resources plugin in Grails 1.4 to implement more performance tweaks, including this view?

comment:7 Changed 5 years ago by work@…

  • Milestone changed from 0.8.3 to 0.8.4

comment:8 Changed 5 years ago by business@…

  • Status changed from reopened to closed
  • Resolution set to worksforme

Study 'linea23' (700+ samples) takes about 2s loading time in Firefox on my Macbook. It can probably be tweaked to load faster (also this might be a server cache hit, I made sure it's not a client side cache hit). However, 2s is acceptable to me. Can others report their times?

comment:9 Changed 5 years ago by robert@…

Maybe something has happened in between. The loading times are acceptable here as well (2-4 seconds). I also tried creating a new study with 500 samples, to make sure it is not a cache hit.

Note: See TracTickets for help on using tickets.