Modify

Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#4729 closed defect (fixed)

josm >= 3116 extremely slow and laggy

Reported by: glebius Owned by: jttt
Priority: major Milestone:
Component: Core Version:
Keywords: Cc:

Description

Newest versions of josm are extremely slow on FreeBSD 9.0-CURRENT.

JOSM 2561 is running OK on the same system.

Attachments (0)

Change History (8)

comment:1 Changed 10 years ago by glebius

Owner: changed from team to jttt

I have made a a binary search through SVN revisions, and found that the r3116 is the one to blame:

r3116 | jttt | 2010-03-11 23:01:49 +0300 (чт, 11 мар 2010) | 1 line
Reuse offscreenBuffer if layers didn't change

Now I need to stick to 3115, because newer versions are almost unusable.

comment:2 Changed 10 years ago by anonymous

Summary: josm 3128, 3129 extremely slow and laggyjosm >= 3116 extremely slow and laggy

comment:3 Changed 10 years ago by jttt

Is it slow (ie full cpu usage) or laggy (it takes some time before layer is refreshed)?

comment:4 Changed 10 years ago by jttt

It's possible that it's slow because of missing double buffering (which was useless on linux, but might be different on FreeBSD). Plese try customized josm from http://jttt.110mb.com/josm-custom.jar and let me know if it makes any difference.

comment:5 in reply to:  4 Changed 10 years ago by bastiK

Replying to jttt:

It's possible that it's slow because of missing double buffering

If that's the case, you might see it draw one line after the other. Normally it should display everything at once.

comment:6 Changed 10 years ago by glebius

Plese try customized josm from http://jttt.110mb.com/josm-custom.jar and let me know if it makes any
difference.

This jar works fine, with no lags. Thanks.

Is it slow (ie full cpu usage) or laggy (it takes some time before layer is refreshed)?

It is laggy. The CPU usage is not full. The java process state is usually "ucond", which means waiting on userland mutex.

comment:7 Changed 10 years ago by jttt

Resolution: fixed
Status: newclosed

(In [3136]) Fix #4729 josm >= 3116 extremely slow and laggy

comment:8 Changed 10 years ago by skyper

Thanks for the fix.

I have to recheck but on a really slow GNU Debian Lenny, r3107 was much faster than r3031 of cource running openjdk.

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain jttt.
as The resolution will be set.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.