All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 15344] New: Gradual Performance Decline With Nouveau Driver
Date: Thu,  3 Apr 2008 11:49:08 -0700 (PDT)	[thread overview]
Message-ID: <bug-15344-8800@http.bugs.freedesktop.org/> (raw)

http://bugs.freedesktop.org/show_bug.cgi?id=15344

           Summary: Gradual Performance Decline With Nouveau Driver
           Product: xorg
           Version: git
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
        AssignedTo: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
        ReportedBy: dgoodwin-eRDYlh02QjtL43Ps8y5oD9BPR1lH4CV8@public.gmane.org
         QAContact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org


Created an attachment (id=15661)
 --> (http://bugs.freedesktop.org/attachment.cgi?id=15661)
My current xorg.conf.

Noticing a steady and significant decline in X performance when rendering large
changes to what's on screen. (eg. switching workspaces or Firefox tabs)

When X is first started everything behaves nicely with performance similar to
what I'm used to with the nvidia driver. However within an hour or two
significant lag starts to develop when navigating and CPU usage seems to be
spiking quite hard while the rendering is taking place. ('top' indicates the
process is X) Window borders are visible somewhat quickly but the contents of
those windows seems to be what takes the most time to appear.

Replicated using Openbox window manager and about 6 workspaces, although only 3
in use with approximately 4 Gnome terminals open and one Firefox instance. OS
is Fedora 9 beta.

Will attach xorg.conf and X log below.

Please let me know if there is any additional info I can provide or particular
things to test to help isolate the issue I'm seeing.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

             reply	other threads:[~2008-04-03 18:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-03 18:49 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-15344-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2008-04-03 19:00   ` [Bug 15344] Gradual Performance Decline With Nouveau Driver bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-03 20:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-03 20:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-04  5:41   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-04 16:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-04 17:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-30  8:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-30  8:39   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2008-04-30  9:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-09-23 10:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-09-26 15:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2009-09-26 15:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-15344-8800@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.