Thanks, my settings are: Minimum block size = 2097152 Maximum block size = 4194304
Unfortunately there was no improvement. Do you offer Enterprise support? The ability to use Ceph in practical terms is very important for us, and I think in general going forward. RAID is getting fairly impractical when you have boxes with 12x 6TB disks that can still only lose 2, and take forever to rebuild at that size. Thanks. On Saturday, March 19, 2016 at 2:23:53 AM UTC-7, marco.van.wieringen wrote: > On 03/19/16 09:50 AM, Fox Whittington wrote: > > In short: We have BareOS DIR & SD on one fast new host with 40TB of local > > storage. > > > > Out entire network is 1Gi, much of it 10Gi and 40Gi. > > > > Our test example backup client will transfer at about 80 to 90MB/sec > > average for the duration of its 4TB backup to the local storage pool. > > > > Using the RADOS gateway with BareOS to Ceph we are getting 3MB/sec average. > > > > Using the RADOS benchmark test from same BareOS host we are getting about > > 68MB/sec to Ceph > > > > Other clients to our 12-node Ceph cluster get pretty good performance from > > other hosts, around the same 68MB/sec. > > > > Have others experienced that performance to Ceph with RADOS -when- using > > BareOS is impractically awful? There is no way we can run huge backups > > with 3MB/sec, making Ceph useless for us with BareOS. > > Currently some of the backend drivers are more proof of concept then anything > else. > I know some people testing the backends to rados as we got some enhancement > request > which we implemented recently. What is probably killing you is the fact that > by > default the blocksize used on any BAREOS file device is the POSIX default e.g. > 512 * 126 = 64,512. Don't know what the benchmark test uses for chunks but > setting > the blocksize on the rados device definition in your bareos-sd.conf will > probably > crank the speed up. There are some disadvantages of setting the blocksize in > the > device however, the docs have quite extensive explanations on how to tune the > blocksize > which is essentially the same for each type of device. I would also setup > things as disk > to disk to rados backups e.g. utilizing the local storage as primary storage > and use > copy/migration jobs to the rados storage. An other thing people are trying is > using the > rados striper functionality for which you need the current experimental > branch as my > initial implementation had some errors. > > > -- > Marco van Wieringen [email protected] > Bareos GmbH & Co. KG Phone: +49-221-63069389 > http://www.bareos.com > > Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646 > Komplementär: Bareos Verwaltungs-GmbH > Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens, > P. Storz, M. v. Wieringen -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
