Bug 92968 - OpenScad has lousy performance
Summary: OpenScad has lousy performance
Status: RESOLVED MOVED
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/nouveau (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Nouveau Project
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-16 10:59 UTC by Roger Wolff
Modified: 2019-09-18 20:41 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Roger Wolff 2015-11-16 10:59:49 UTC
OpenScad performance is WAY less than what I'm used to. This is with new hardware and a more recent ubuntu version. 

Suggestion on the mailing list: disable vblank syncing. I was unable to do this. The environment variable setting that works for glxgears does not influence the behaviour of openscad. I was unable to achieve disabling the option in the X server. 

Suggestions on the IRC channel led me to try installing an older version. I created an chrooted ubuntu 14.04 environment. The openscad in there provides reasonable performance. 

I then recompiled the current git version of openscad in the chrooted 14.04 environment, and that too provides reasonable performance. 

So: Without changing the X server (or its configuration) it is possible to achieve good performance. Also, the source of openscad is not the culprit, but the libraries linked to. 

This does not mean that it is not an openscad bug: It could very well be that openscad requests a feature that was unimplemented on earlier libraries.
Comment 1 GitLab Migration User 2019-09-18 20:41:49 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1091.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.