Page MenuHomekolab.org

Investigate and fix memory consumption/performance of PhantomJS
Open, NormalPublic8 Story Points

Details

Ticket Type
Task

Event Timeline

Adityab created this task.Aug 17 2015, 4:12 PM
Adityab updated the task description. (Show Details)
Adityab raised the priority of this task from to 60.
Adityab claimed this task.
Adityab changed Ticket Type from Task to Task.
Adityab added subscribers: vanmeeuwen, grote, Adityab.
petersen added a project: Restricted Project.Aug 17 2015, 4:13 PM
Adityab edited a custom field.Aug 17 2015, 4:14 PM
Adityab moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Aug 19 2015, 1:29 AM

Unscientific observations so far:

  1. Killing the phantom process once it's session is closed seems to help
  2. Noticeable improvement seen after loading snapshots into phantom instead of doing the entire first replay there.
Adityab moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Aug 21 2015, 6:57 PM
Adityab moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Sep 7 2015, 10:42 AM
  1. Setting the exported snapshot buffer to undefined should encourage the GC to remove it from memory later. A noticeable improvement occured.
  2. A genuinely significant improvement would be to exchange the snapshots over socketio instead of the node-phantomjs library's bridge (which is seriously inefficient and a minefield of memory leaks).
vanmeeuwen lowered the priority of this task from 60 to Normal.Mar 28 2019, 8:13 AM