Bug 26625 - Really slow microsoft visio (wine)
Summary: Really slow microsoft visio (wine)
Status: RESOLVED INVALID
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-18 05:12 UTC by Jaime
Modified: 2016-02-25 02:09 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
xorg log (94.63 KB, patch)
2010-02-18 05:28 UTC, Jaime
no flags Details | Splinter Review

Description Jaime 2010-02-18 05:12:08 UTC
Hi,

Visio 2003 (wine) works like a charm on ubuntu karmic and fglrx drivers.

But today i tried on ubuntu lucid + xorg edgers (radeon OSS drivers), and it works 100 times slower, zooming in and out is a pain, objects are drawn 1 by 1... Is really really slow.

Regards
Jaime
Comment 1 Jaime 2010-02-18 05:28:50 UTC
Created attachment 33385 [details] [review]
xorg log
Comment 2 Ernst Sjöstrand 2010-02-18 08:08:58 UTC
I don't have Visio so I can't test that, but how is graphics otherwise?
I have almost the same setup but with a 4770 and I've never seen such fast graphics. gtkperf? :-)
Running compiz?
Comment 3 Jaime 2010-02-18 10:57:10 UTC
Hi Ernst,

I am not a 3d user, no compiz, i use basically video ,browser and office aplications. So for me all is working fine, but wine + visio.

What really hesitates me, is that radeon OSS has a very good 2D performance, and a reputation on that. And i dont understand why wine + fglrx is much faster than wine + radeon oss on visio application. 

Is wine using xrender for 2d applications such visio? has radeon oss a bad xrender implementation (i doubt)? a vsync problem? what is happening?

Regards
Jaime

Comment 4 Jaime 2010-02-18 11:01:05 UTC
GtkPerf 0.40 - Starting testing: Thu Feb 18 20:00:05 2010

GtkEntry - time:  0,07
GtkComboBox - time:  2,00
GtkComboBoxEntry - time:  2,00
GtkSpinButton - time:  0,15
GtkProgressBar - time:  0,08
GtkToggleButton - time:  0,16
GtkCheckButton - time:  0,11
GtkRadioButton - time:  0,18
GtkTextView - Add text - time:  1,34
GtkTextView - Scroll - time:  0,22
GtkDrawingArea - Lines - time:  2,29
GtkDrawingArea - Circles - time:  3,73
GtkDrawingArea - Text - time:  3,26
GtkDrawingArea - Pixbufs - time:  1,46
 ---
Total time: 17,06
Comment 5 Alex Deucher 2010-02-18 11:08:56 UTC
(In reply to comment #3)
> What really hesitates me, is that radeon OSS has a very good 2D performance,
> and a reputation on that. And i dont understand why wine + fglrx is much faster
> than wine + radeon oss on visio application. 
> 
> Is wine using xrender for 2d applications such visio? has radeon oss a bad
> xrender implementation (i doubt)? a vsync problem? what is happening?

You'll probably want to ask the wine folks or profile it to see what slow path is being hit.
Comment 6 Clemens Eisserer 2010-02-18 14:40:56 UTC
if you've some spare time left, sysprof is a really handy tool to find out where all the time is spent system-wide.

Fglrx is almost pure software (cpu) rendering, so applications behaving "bad" don't cause much troubles. I doubt this is a RENDER fallback.
Comment 7 Michel Dänzer 2015-04-23 02:05:46 UTC
With current xf86-video-ati Git master, does enabling the following options in /etc/X11/xorg.conf help?

 Option "AccelMethod" "glamor"
 Option "ShadowPrimary"
 Option "TearFree"
Comment 8 Christopher M. Penalver 2016-02-25 02:09:14 UTC
Jaime, Ubuntu Karmic reached EOL on April 30, 2011. For more on this, please see https://wiki.ubuntu.com/Releases .

If this is reproducible in a supported release, it will help immensely if you filed a new report with Ubuntu by ensuring you have the package xdiagnose installed, and that you click the Yes button for attaching additional debugging information running the following from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.


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.