Graphics performance on NewVM laggy.

[GoogleCodeExporter]

Responsiveness on new vm is noticeably slower than on the old vm.  I will post 
a simple sample app to demonstrate - right now I'm using some real-world apps 
and noticing this.

Steps:

1. A list with a custom renderer (just an image and text) with enough items to 
scroll ( at least 20 or so).
2. Scroll list up and down with index finger at varying speeds.

In old VM the list scroll is quite responsive, staying with the finger.
On new VM the list scroll is laggy, often times a full up-down movement behind.

This issue should lead to two activities:

1.  Work on improving graphics pipeline efficiency.
2. Work on improving performance of VM in general.

Original issue reported on code.google.com by steve.ha...@codenameone.com on 31 Jan 2015 at 1:57

[GoogleCodeExporter]

That's a GC regression discussed in the forum. Its already fixed.

Original comment by shai.almog on 31 Jan 2015 at 6:17

• Changed state: Invalid

[GoogleCodeExporter]

Yes.  Just tried out the latest updates you made and it does help.  It is now 
only slightly more laggy on the New VM - but not as noticeable as before.  I'll 
put together a test case.  Creating quantifiable benchmarks for graphics is 
tricky since it is asynchronous (i.e. you can't just measure the time for the 
graphics calls - it also involves drawing the frame in OGL).

Original comment by steve.ha...@codenameone.com on 31 Jan 2015 at 1:47

• Changed state: Accepted
• Added labels: Priority-Low
• Removed labels: Priority-High