Re: [Openstack] [Swift] [Storage node] Lots of timeouts in load test after several hours around 1, 000, 0000 operations

2012-07-10 Thread Kuo Hugo
Hello , folks Seems most of time consumed by the following code in obj/server.py iter(lambda: reader(self.network_chunk_size), '') L591 - L605 https://github.com/openstack/swift/blob/master/swift/obj/server.py#L591 10323 Jul 10 14:34:42 object-server WTF: InitTime: 0.000183#012 SavingTime: 0

Re: [Openstack] [Swift] [Storage node] Lots of timeouts in load test after several hours around 1, 000, 0000 operations

2012-07-03 Thread Kuo Hugo
I found that updater and replicator could improve this issue. In my original practice , for getting best performance , I only start main workers ( account-server , container-server , object-server) , And keep upload / download / delete objects over 100 times. Issues: 1. XFS or Swift consumes

Re: [Openstack] [Swift] [Storage node] Lots of timeouts in load test after several hours around 1, 000, 0000 operations

2012-07-01 Thread Kuo Hugo
An update about 76667 Jul 1 16:37:50 angryman-storage-03 kernel: [350840.052654] w83795 0-002f: Failed to read from register 0x015, err -6 error seems come with lm-sensors to collect HW temperature . It might be an alert of system. 2012/7/2 John Dickinson > I hope you are able to get an answ

Re: [Openstack] [Swift] [Storage node] Lots of timeouts in load test after several hours around 1, 000, 0000 operations

2012-07-01 Thread John Dickinson
I hope you are able to get an answer. I'm traveling this week, so I won't have a chance to look in to it. I hope some of the other core devs will have a chance to help you find an answer. --John On Jul 1, 2012, at 2:03 PM, Kuo Hugo wrote: > Hi all , > > I did several loading tests for swif

[Openstack] [Swift] [Storage node] Lots of timeouts in load test after several hours around 1, 000, 0000 operations

2012-07-01 Thread Kuo Hugo
Hi all , I did several loading tests for swift in recent days. I'm facing an issue ... Hope you can share you consideration to me ... My environment: Swift-proxy with Tempauth in one server : 4 cores/32G rams Swift-object + Swift-account + Swift-container in storage node * 3 , each for : 8