Re: [Bacula-users] very slow virtualfull job

2013-04-29 Thread Josh Fisher
On 4/29/2013 8:05 AM, James Harper wrote: >> On Mon, Apr 29, 2013 at 08:33:42AM +, James Harper wrote: >>> When loading the data into postgresql absolutely crawled along >> (~50kb/second disk write speed with 100% iowait) I knew I had a problem. >>> Something, somewhere has changed in my syste

Re: [Bacula-users] very slow virtualfull job

2013-04-29 Thread James Harper
> > On Mon, Apr 29, 2013 at 08:33:42AM +, James Harper wrote: > > When loading the data into postgresql absolutely crawled along > (~50kb/second disk write speed with 100% iowait) I knew I had a problem. > > Something, somewhere has changed in my system that absolutely kills tiny > sync writes

Re: [Bacula-users] very slow virtualfull job

2013-04-29 Thread Adrian Reyer
On Mon, Apr 29, 2013 at 08:33:42AM +, James Harper wrote: > When loading the data into postgresql absolutely crawled along (~50kb/second > disk write speed with 100% iowait) I knew I had a problem. > Something, somewhere has changed in my system that absolutely kills tiny sync > writes. Or al

Re: [Bacula-users] very slow virtualfull job

2013-04-29 Thread James Harper
> Hello James, > > It looks like you have found the most important things: turn on > attribute spooling, This actually made it worse. Instead of distributing the tiny little writes throughout the backup job, it saved them all to the end when nothing else was running. It would be nice if the nex

Re: [Bacula-users] very slow virtualfull job

2013-04-29 Thread Kern Sibbald
Hello James, It looks like you have found the most important things: turn on attribute spooling, and switch to InnoDB. Before switching to PostgreSQL, you might try running the MySQL tunning program mysqltune (I forgot the exact name). It tells you items you should tune. Often users do not gi

Re: [Bacula-users] very slow virtualfull job

2013-04-26 Thread James Harper
> > On Thu, Apr 25, 2013 at 11:41:37PM +, James Harper wrote: > > What could have gone wrong with my mysql to make this happen? I've > tried rebooting it. > > You very likely use MySQL with MyISAM tables. This is a very bad > combination for bacula. It will be better with InnoDB tables and >

Re: [Bacula-users] very slow virtualfull job

2013-04-26 Thread Adrian Reyer
On Thu, Apr 25, 2013 at 11:41:37PM +, James Harper wrote: > What could have gone wrong with my mysql to make this happen? I've tried > rebooting it. You very likely use MySQL with MyISAM tables. This is a very bad combination for bacula. It will be better with InnoDB tables and correctly tune

Re: [Bacula-users] very slow virtualfull job

2013-04-25 Thread James Harper
> > My setup has suddenly slowed down when running virtualfull jobs. I don't > think it's all virtualfull jobs as if I kill off the one that's stalled then > a few more > run okay until it hits another bad one. > > iostat on the sd shows pretty much nothing happening most of the time... > bursts

[Bacula-users] very slow virtualfull job

2013-04-24 Thread James Harper
My setup has suddenly slowed down when running virtualfull jobs. I don't think it's all virtualfull jobs as if I kill off the one that's stalled then a few more run okay until it hits another bad one. iostat on the sd shows pretty much nothing happening most of the time... bursts of 1MB/second