OpenRefine / OpenRefine/OpenRefine
really slow rendering in browser
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 12k
- Forks
- 2.2k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 27
Description
Original author: libo...@gmail.com (June 11, 2012 12:24:49)
What steps will reproduce the problem?
- Load attached xml data (same as in issue #137).
- Even the initial display is really slow.
- Click 'next>>' in the pager.
What is the expected output? What do you see instead?
It takes about 25 seconds on 4 GB Xeon E31245 to render 10 records (about 80 rows). A second or two for rendering would be acceptable. See attached screenshot.
What version of Google Refine are you using?
Tried with 2.5 and SVN trunk checkout.
What operating system and browser are you using?
Win7, Chrome 19 and Opera 11, both browsers go haywire.
In issue #137 @tfmorris noticed that this could be caused by large number of null cells. Can someone verify this?
Original issue: http://code.google.com/p/google-refine/issues/detail?id=583
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the slowdown with the XML data from issue #137 in Chrome or Opera, checking both the initial display and the pager's next page. Profile browser rendering for 10 records and about 80 rows; done when rendering takes roughly 1–2 seconds instead of 25 seconds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- frontend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100