[Bug 262867] Re: cd burning io locks the cpu

[Daniel Hollocher]

** Description changed:

- Brasero uses /tmp for its temporary work space.  /tmp is just a
- directory on the harddrive, its not RAM.  Thus, when brasero tries to do
- a bunch of work, it ends up swapping to the harddrive, even though you
- have plenty of ram.
+ I reported this bug thinking that it was an issue with /tmp, as you can
+ see below.  But since then, I have tested much more, and the issue
+ "feels" like DMA is turned off.
+ 
+ I recently tested burning on Windows, and I realized that I had
+ forgotten how fast a computer I have.  On windows, I can burn the cd
+ without any slow downs; I can even defrag my harddrive without a hiccup.
+ 
+ The cd that I burn is a rw, and it burns quote slow, only 4x.  But, on
+ linux, that is enough to drag to a stand still, and the system monitor
+ reports the cpu burning away in io wait.
+ 
+ I have tested with brasero of course, but also allot with k3b, on
+ several clean installs including a 64bit.
+ 
+ I have a P5B motherboard: http://asus.com/product.aspx?P_ID=YwIVDOTcvIMHZdTy
+ My cd rom and HDD are both hooked into the IDE cable, which I believe is the jmicron controller.  (the mobo is geared toward SATA, but I built this as an upgrade from a computer geared towards PATA, and just used the HDD and CD from that)
+ 
+ 
+ --old--
+ Brasero uses /tmp for its temporary work space.  /tmp is just a directory on the harddrive, its not RAM.  Thus, when brasero tries to do a bunch of work, it ends up swapping to the harddrive, even though you have plenty of ram.
  
  The work around is to go into properties, and use any tmpfs mount point,
  which uses the RAM, like /dev/shm
  
  I guess /tmp is for temporary files that you aren't doing allot of I/O
  on.  Anyway, I don't really know whats going on.  I don't know why
  brasero is using files in the first place.  I switched, and saw no
  noticeable increase in my ram usage, so its not like brasero needs a
  large working space.  I don't understand why brasero isn't just
  allocating the memory it needs, like every other program does.

-- 
cd burning io locks the cpu
https://bugs.launchpad.net/bugs/262867
You received this bug notification because you are a member of Kernel
Bugs, which is subscribed to Linux.