Tuesday, 2014-02-18

openstackgerritA change was merged to openstack/swift: Handle COPY verb in container quota middleware  https://review.openstack.org/6118100:10
*** zigo has quit IRC00:25
*** zigo has joined #openstack-swift00:26
*** matsuhashi has joined #openstack-swift00:28
*** joeljwright has joined #openstack-swift00:28
*** joeljwright has quit IRC00:32
*** zigo has quit IRC00:42
bsdkurtin a three copy cluster, for object GET, how does the proxy server decide which copy to retrieve?00:49
tburnesFor a production cluster, is there any documentation or guidance from the community on best practice for security of information?00:49
*** MirandaZhang has joined #openstack-swift00:55
*** zigo has joined #openstack-swift00:59
*** zigo has quit IRC01:08
*** zigo has joined #openstack-swift01:13
*** shri has quit IRC01:14
MirandaZhangcould anyone help me with the swift client problem https://ask.openstack.org/en/question/12155/swiftclient-202-importerror/01:14
*** zigo has quit IRC01:20
*** zigo has joined #openstack-swift01:22
notmynamemordred: I haven't been online today. I just sat down briefly (ie can't stay now) and saw you mentioned some "known problem with swift and grenade". something I need to take a look at later?01:25
*** zigo has quit IRC01:27
mordrednotmyname: I think mtreinish has it01:27
notmynamemordred: k, thanks. I'll be able to check in later if anything's needed01:27
mordrednotmyname: swiftclient release removed a call that stable/grizzly swift tests were using, aiui01:27
notmynamehmmm01:27
mordrednotmyname: which means that grenade had an issue01:27
* mordred waves hands in air01:28
notmynamewell that's what you get when you play with grenades!01:28
*** zigo has joined #openstack-swift01:28
notmynameok, I'm out again. I'll check in this evening later01:28
*** joeljwright has joined #openstack-swift01:29
*** nosnos has joined #openstack-swift01:33
*** joeljwright has quit IRC01:34
openstackgerritA change was merged to openstack/python-swiftclient: Add option to skip downloading/uploading identical files  https://review.openstack.org/6547001:45
*** Diddi has quit IRC01:50
*** zigo has quit IRC01:51
*** Diddi has joined #openstack-swift01:52
*** zigo has joined #openstack-swift01:53
*** zigo has quit IRC02:04
*** Diddi has quit IRC02:05
*** zigo has joined #openstack-swift02:06
*** Diddi has joined #openstack-swift02:07
*** joeljwright has joined #openstack-swift02:31
*** zigo has quit IRC02:35
*** joeljwright has quit IRC02:35
*** zigo has joined #openstack-swift02:48
*** zackf has quit IRC03:06
*** ppai has joined #openstack-swift03:18
*** matsuhashi has quit IRC03:23
notmynamehola03:26
*** joeljwright has joined #openstack-swift03:32
*** joeljwright has quit IRC03:39
openstackgerritThomas Goirand proposed a change to openstack/python-swiftclient: swift.1 manpage fix for groff warnings  https://review.openstack.org/7424903:49
luisbgnotmyname, hola04:01
notmynameluisbg: good evening04:01
luisbgno en español?04:02
notmynameheh. my son is in spanish immersion in kindergarten. but I know basically no spanish (other than the little you pick up growing up in Texas)04:03
luisbgso your kid can use it as a secret language between his friends04:05
notmynameya, no kidding. he and my wife already do :-)04:07
luisbgnotmyname, muy bien por ellos! :)04:15
openstackgerritJohn Dickinson proposed a change to openstack/swift: Make PBR based setup completely optional  https://review.openstack.org/7373804:17
luisbgnotmyname, copyright said Hewlett Packard?04:18
notmynamethe old version of that file what contributed by HP04:19
notmynameerr..current04:19
luisbgsoon to be old version04:21
luisbgnotmyname, I feel a bit like a fool tempted to +1 your review :P04:22
notmynameluisbg: well, it's actually a very contentious patch.04:22
*** pberis has quit IRC04:24
luisbgnotmyname, ahhhh I see (about copyright dates)04:28
notmynameya04:28
luisbgthanks for clarifying04:30
*** Dharmit has joined #openstack-swift04:34
*** joeljwright has joined #openstack-swift04:35
*** joeljwright has quit IRC04:40
luisbgnotmyname, I am having some tests pass on my machine using tox, but not pass on Jenkins, is there a way to avoid spamming the review with changes/rechecks trying to figure out why?04:42
notmynameluisbg: depends on what's failing in jenkins04:42
notmynameis it swift jobs that are failing?04:42
*** matsuhashi has joined #openstack-swift04:43
luisbgnotmyname, no04:44
luisbgthis is a patch for a small bug in oslo.config04:44
notmynameah04:44
*** Dharmit has quit IRC04:44
notmynameluisbg: so in that case, you're seeing all the tests pass locally in devstack?04:45
* notmyname assumes that oslo is using devstack as a dev environment04:45
luisbgnotmyname, well, machine where I have devstack, running tox in the oslo.config git clone04:45
notmynameyou have now reached the end of my knowledge about testing patches for oslo04:46
luisbgnotmyname, hahahahahaa04:46
luisbgsorry about that04:46
luisbgshould I just mention this in the gerrit review and see if somebody who knows oslo.config suggests something?04:46
notmynameya. or find someone on IRC04:48
*** matsuhashi has quit IRC05:09
*** matsuhashi has joined #openstack-swift05:09
*** matsuhashi has quit IRC05:10
*** matsuhashi has joined #openstack-swift05:10
openstackgerritJohn Dickinson proposed a change to openstack/swift: Make PBR based setup completely optional  https://review.openstack.org/7373805:13
notmynamewow pep8 thanks!05:13
* notmyname only likes pep8 when it doesn't catch issues in his own code05:13
*** chandan_kumar has joined #openstack-swift05:20
*** gvernik_ has joined #openstack-swift05:26
*** nosnos has quit IRC05:33
*** nosnos has joined #openstack-swift05:34
*** joeljwright has joined #openstack-swift05:36
*** matsuhashi has quit IRC05:36
*** matsuhashi has joined #openstack-swift05:37
*** matsuhas_ has joined #openstack-swift05:38
*** matsuhashi has quit IRC05:39
*** joeljwright has quit IRC05:40
*** rturk-away has quit IRC05:43
*** rturk-away has joined #openstack-swift05:48
*** nshaikh has joined #openstack-swift05:57
*** rturk-away has quit IRC05:59
*** rturk-away has joined #openstack-swift06:02
*** bsdkurt has quit IRC06:07
*** nosnos_ has joined #openstack-swift06:10
*** nosnos has quit IRC06:10
openstackgerritA change was merged to openstack/python-swiftclient: Only run flake8 on swiftclient code  https://review.openstack.org/7350706:22
openstackgerritA change was merged to openstack/python-swiftclient: Add missing backslash.  https://review.openstack.org/7122406:25
openstackgerritA change was merged to openstack/swift: Added docs about the swift_source log field  https://review.openstack.org/7116306:29
*** joeljwright has joined #openstack-swift06:37
*** joeljwright has quit IRC06:42
*** zaitcev has quit IRC06:46
*** saju_m has joined #openstack-swift06:48
*** ppai has quit IRC06:56
*** Dharmit has joined #openstack-swift06:59
*** gvernik_ has quit IRC06:59
*** foexle has joined #openstack-swift07:04
*** ppai has joined #openstack-swift07:13
*** Dharmit has quit IRC07:14
*** nosnos_ has quit IRC07:19
*** nosnos has joined #openstack-swift07:19
*** bsdkurt has joined #openstack-swift07:35
*** joeljwright has joined #openstack-swift07:38
*** joeljwright has quit IRC07:42
*** mlipchuk has joined #openstack-swift07:47
*** kris_h has quit IRC07:53
*** MirandaZhang has left #openstack-swift08:06
*** joeljwright has joined #openstack-swift08:10
*** Dharmit has joined #openstack-swift08:33
*** mmcardle has joined #openstack-swift08:41
*** nacim has joined #openstack-swift08:47
*** nshaikh has left #openstack-swift09:00
*** chandankumar_ has joined #openstack-swift09:02
*** chandan_kumar has quit IRC09:03
*** mkollaro has joined #openstack-swift09:13
*** fbo_away is now known as fbo09:23
*** saju_m has quit IRC09:37
*** saju_m has joined #openstack-swift09:37
*** nosnos has quit IRC09:41
*** nosnos_ has joined #openstack-swift09:41
*** saju_m has quit IRC09:46
*** kris_h has joined #openstack-swift09:48
*** saju_m has joined #openstack-swift10:05
*** kris_h has quit IRC10:27
*** chandan_kumar has joined #openstack-swift10:30
*** chandankumar_ has quit IRC10:34
openstackgerritA change was merged to openstack/swift: Allow log disable in account/container server  https://review.openstack.org/7412811:02
openstackgerritTristan Cacqueray proposed a change to openstack/python-swiftclient: Add requests related unit-tests  https://review.openstack.org/7432811:02
*** nosnos_ has quit IRC11:43
*** nosnos has joined #openstack-swift11:44
openstackgerritDonagh McCabe proposed a change to openstack/swift: Improve StaticWeb 404 on web-listings/index  https://review.openstack.org/7433611:46
*** nosnos_ has joined #openstack-swift12:43
*** nosnos has quit IRC12:43
*** bingbu has joined #openstack-swift13:01
*** matsuhas_ has quit IRC13:04
*** mlipchuk has quit IRC13:04
*** mkollaro has quit IRC13:06
*** matsuhashi has joined #openstack-swift13:06
*** mkollaro has joined #openstack-swift13:06
*** ppai has quit IRC13:14
*** mlipchuk has joined #openstack-swift13:23
*** rando has joined #openstack-swift13:25
*** mdonohoe has quit IRC13:26
*** mmcardle has quit IRC13:37
*** bingbu has quit IRC13:44
*** saju_m has quit IRC13:50
*** mmcardle has joined #openstack-swift13:53
*** mkollaro has quit IRC13:56
*** mkollaro1 has joined #openstack-swift13:56
*** Trixboxer has joined #openstack-swift13:57
*** pconstantine has quit IRC14:05
*** pconstantine has joined #openstack-swift14:07
*** tdasilva has joined #openstack-swift14:07
*** tongli has joined #openstack-swift14:08
*** mlipchuk has quit IRC14:08
*** zul has quit IRC14:09
*** zul has joined #openstack-swift14:11
*** mlipchuk has joined #openstack-swift14:14
*** kris_h has joined #openstack-swift14:16
*** pberis has joined #openstack-swift14:44
*** foexle has quit IRC14:46
*** jergerber has joined #openstack-swift14:52
*** nosnos_ has quit IRC14:57
*** dmsimard has joined #openstack-swift14:57
*** mkollaro has joined #openstack-swift15:02
*** mkollaro1 has quit IRC15:02
*** donagh has joined #openstack-swift15:04
mtreinishnotmyname: so the issue wasn't actually swift but the devstack exercises which use swiftclient, it's a python install/requirements issue because grizzly has a version cap < 2 but we install from master during grenade15:15
notmynamemtreinish: ah. gotcha. so it was the major version bump then?15:16
mtreinishnotmyname: yeah15:16
notmynamemtreinish: anything I should have done differently in the 2.X release?15:16
mtreinishthere is a swift issue too but only if you guys ever want to backport something to the stable/grizzly branch (one of the functional tests that uses swiftclient)15:16
notmynamemtreinish: ok. can you give me a link?15:17
mtreinishnotmyname: no, I think it's more the state of global reqs in grizzly, I pushed an uncap but it didn't fix it15:17
mtreinishnotmyname: sure let me dig it up one sec15:17
*** zackf has joined #openstack-swift15:17
mtreinishnotmyname: https://review.openstack.org/#/c/74150/15:18
mtreinishthe requests move dropped the HTTPException class from swiftclient15:19
notmynameright. got it. so aside from a porr commit message, do you know the reason it was abandoned?15:20
mtreinishwell I think he jumped the gun because the cells job still failed which is the install issue15:20
mtreinishwhich I still have to figure out how to unwedge15:21
*** mkollaro1 has joined #openstack-swift15:21
*** mkollaro has quit IRC15:21
notmynamemtreinish: seems like it would be reasonable to keep grizzly (and other stable releases for that matter) at <2.15:23
mtreinishnotmyname: the issue with that is we run all the tests with master branches of the clients15:23
mtreinishso when you push a major release it will cause issues15:24
notmynameperhaps that's not a good idea with historic stable releases15:24
*** chandan_kumar has quit IRC15:43
*** byeager has joined #openstack-swift15:45
openstackgerritConstantine Peresypkin proposed a change to openstack/swift: account to account copy implementation  https://review.openstack.org/7215715:48
mjsegernotmyname: I've been doing some testing over the weekend and today with swiftclient V2 and am finding what appears to be a significant drop in performance and am wondering if you or others have seen that as well15:51
tristanCmjseger: was it 2.0.2 ?15:55
openstackgerritAlistair Coles proposed a change to openstack/swift: Fix invalid account acl generating 500 response.  https://review.openstack.org/7441715:56
creihtmjseger: heh... I was actually planning on doing some testing with that15:56
creihtbut haven't done that yet15:56
mjsegerit was the one announced on the openstack list.  hang on a sec15:56
tristanC2.0 and 2.0.1 have a memory hog bug fixed in 2.0.215:57
mjsegeryes, 2.0.215:57
mjsegerssegerm@az1-nv-compute-0003:~$ swift --version swift 2.0.215:57
mjsegerif anyone would like to try my getput tool, which makes it pretty easy to run test with,  I'll be happy to send you a copy OR just use whatever mechanisms you normally use15:58
mjsegerwhat I also found is it's not just limited to small objects and even large PUTs look like they suffer15:58
*** Dharmit has quit IRC15:59
mjsegerI even tried timing 'swift upload' commands for large objects and found them to be slowed with 2.0.2 than 1.915:59
acolesotherjon: could you cast an eye over https://review.openstack.org/#/c/74417 . thanks16:00
mjsegerone other thing I found is if I install 2.0.2 from the tarball and then try to downgrade to 1.9 I can't!  it doesn't replace client.py with the older one.  shouldn't it?16:00
*** Dharmit has joined #openstack-swift16:03
tristanCmjseger: I notice a 4.2% drop in performance between 2.0.2 and 1.9 (time swift upload)16:08
mjsegertristanC: i16:08
mjsegertristanC: I've actually found measuring single operations not to be that accurate.  for my tests I ran 1k and 2k puts for 2 minutes and found almost a 2:1 difference between the IOPS for 1.9 and 2.016:10
mjsegerhave you done any testing like that?16:10
tristanChum interesting, no I didn't perform such tests16:14
*** Cotes has joined #openstack-swift16:14
tristanCI'd like to give your "getput tool" a try16:14
notmynamemjseger: thanks for bringing it up16:15
*** Eelis has left #openstack-swift16:16
mjsegernotmyname: is would be good to hear if others can confirm my findings.  also, would you consider if a bug if you can't install 1.9 on top of 2.0.2?  I would...16:17
notmynamemjseger: how are you trying to install it?16:18
*** zackf has quit IRC16:18
*** zackf has joined #openstack-swift16:18
mjsegerI'm using "python setup.py install"16:18
cschwedemjseger: you might need a "python setup.py develop" as well16:20
*** kris_h has quit IRC16:20
mjsegerhmm, so I do that before the install?16:20
creihtmjseger: well, you are just going to have headaches trying to install an older version over a newer version16:21
creihtyou might have to go delete the older version first16:21
creihtwell whatever version you are trying to replace16:21
notmynamelooks like creiht and cschwede are up (thanks!). I'm biking to work now. be back online in ~30 min16:22
mjsegerfrom a purely functional perspective I'd think users should be able to move back and forth between versions, especially if you're trying to benchmark things16:22
creihthah16:22
creihtmjseger: yeah, unfortunately python doesn't make that very easy16:22
cschwedemjseger: not that easy16:22
*** zackf has quit IRC16:22
mjsegerbummer...16:22
cschwedei sometimes use python -c "import swiftclient; print swiftclient" to get the location where a lib has been installed, and then i just delete that path (not the cleanest way i know, but works for me)16:24
mjsegerso that means when install the new swiftcleint and see the performance drop by a factor of 2 I can't go back to the previous version?  do I need to reimage the whole system then?16:24
cschwedemjseger: no, i don't think that this is required16:25
mjsegerahh, I was thinking of doing something like that but didn't want to make things worse.  I'll give that a go16:25
creihtmjseger: well the easist way is probably to clean out any pip installed or packger installed swiftclients16:25
mjsegerso that gets me back to my original question about performance and seeing the drop.  I am testing on different physical boxes but have tried on enough machines that I'm feeling pretty confident about what I'm seeing16:25
creihtby doins something similar to what cschwede is saying16:25
mjsegerI'd be more than happy to share any results16:26
creihtyou can also print swiftclient.__file__16:26
creihtonce you have done that, you could check out the swiftclient versions in different repos16:26
creihtand then I would recommend doing python setup.py develop in whichever one you want to use16:26
creihtthat *should* then overwrite the current version each time16:26
creihtI think16:27
creiht:)16:27
creihtmjseger: and yeah it would be interesting to see your results16:27
cschwedecreiht: sounds like a good plan :)16:27
creihtI was going to run some swift-benchs on a couple of environs with both versions to see what that looks like16:27
mjsegerare there any specific types of tests you'd like to see?  anyhow hang on a sec and I'll rerun and post the results.  should be pretty quick16:28
creihtmjseger: I think the best data is test runs that represent your use cases16:29
mjsegersince I'm doing general purpose benchmarking I have have any specific use cases.16:30
*** matsuhashi has quit IRC16:32
mjsegercreight: wow, I just ran get tests for the first time and those numbers are even worse!  here's my data for 1k and 1M puts/gets: http://paste.openstack.org/show/66941/16:32
cschwedehow is your tool working? is it using client.put_object direct (ie from within a python tool)?16:32
cschwedemjseger: are you deleting all data from your containers before testing?16:33
mjsegergood question, current I'm not but I can rerun the tests with unique container names ot make sure they're brand new.  hang on16:33
cschwedemjseger: uhh!16:33
cschwedemjseger: uhh: i mean the results16:34
cschwede130 vs 30? thats a 4:1 drop :(16:34
cschwedeand looks like cpu usage is significantly higher16:34
mjsegeryes, 4:1.  I just reran with UTC appended to each container name and the overall perforamnce for both dropped by 2.0.2 is still pretty poor16:35
tristanCmjseger: can you share your getput tool ?16:35
cschwedemjseger:  can you share that tool?16:36
cschwede:=16:36
cschwede:)16:36
tristanCmjseger: also, it might be worth mentioning the python-requests version you are using16:36
mjsegerre tool - absolutely.  where shoudl I send it?16:36
mjsegerhere's the results with uynique container names: http://paste.openstack.org/show/66942/16:36
tristanCmjseger: as you wish, github, paste.openstack.org, ...16:37
cschwedeif it is only getput.py, than paste.openstack.org should be fine16:37
mjsegerI'm using requests 2.2.1 I think since that's the one that disables nagel16:37
*** IRTermite has left #openstack-swift16:49
*** byeager has quit IRC16:52
mjsegercschwede: still trying to find the best way to share.  how big a script can you sick into paste.com?  I have a whole tarball with help, man pages, etc.  OR I can paste in getput.py which is about 1700 lines long16:53
*** kris_h has joined #openstack-swift16:55
cschwedemjseger: i discussed the performance issue with tristanC and two questions popped up: 1. are you using ssl cert verification in your tests and 2. are you reusing the http connection?16:55
creihtmjseger: put it up on github? :)16:56
mjsegeryesh, I really do need to get it there.  unfortunately I have a concall in 5 mins but will try to set things up when I'm done16:57
tristanCmjseger: thank you!16:57
cschwedemjseger: great, that would be cool. I'm also leaving in a few minutes for dinner, but will be around later16:57
mjsegercschwede: re ssl and reusing connections, I'm doing what I think is vanilla swftclient call, creating a connection and then doing a bunch of puts, gets, etc.  so i assume that means I'm resusing.  as for ssl, I'm taking the defaults16:58
mjsegergotta run but like the terminator, I'll be back ;)16:58
cschwedemjseger: ok that means a ssl cert check which might slow things down. that behavior changed16:58
* cschwede afk for dinner, will be online later17:00
*** jergerber has left #openstack-swift17:00
mjsegercschwede: but I'd assume the cert check is only done once, so on a large object put wouldn't the time be negligible?17:00
*** zackf has joined #openstack-swift17:02
*** tanee has joined #openstack-swift17:03
tristanCmaybe the requests implementation could use the requests.Session thing, might speed up things. I'll give it a try now17:03
*** lpabon has joined #openstack-swift17:07
*** Midnightmyth has joined #openstack-swift17:08
*** krtaylor has quit IRC17:09
*** lpabon has quit IRC17:12
*** rando has quit IRC17:15
*** wer has joined #openstack-swift17:16
*** mlipchuk has quit IRC17:20
*** kris_h has quit IRC17:22
*** tanee is now known as tane-away17:32
*** krtaylor has joined #openstack-swift17:33
*** gyee has joined #openstack-swift17:45
*** Dharmit has quit IRC17:46
openstackgerritConstantine Peresypkin proposed a change to openstack/swift: account to account copy implementation  https://review.openstack.org/7215717:49
*** nacim has quit IRC17:51
*** mvenesio has joined #openstack-swift17:54
mjsegercschwede: I think I have something in github, though never having created a repository no promises it's completely correct ;)  but here it is: https://github.com/markseger/getput (I think)17:57
mjsegercschwede:  if you indeed can see it and want to try something real simple, just pull down getput.py and I can tell you ina few seconds what commands you need run17:58
*** joeljwright has quit IRC18:06
mjsegertristanC: notmyname: in case you didn't see my message to cschwede, you can pull a copy of getput from github now.  I'd really like to get some independent confirmation of what I'm seeing18:06
*** mkollaro1 has quit IRC18:09
openstackgerritJon Snitow proposed a change to openstack/swift: Return a 400 when a non-dict JSON ACL is posted.  https://review.openstack.org/7445918:13
openstackgerritJon Snitow proposed a change to openstack/swift: Return a 400 when a non-dict JSON ACL is posted.  https://review.openstack.org/7445918:19
gholttorgomatic: dfg mentioned that the tempurl isn't a big deal (right now) because you can only make tempurls if you have account admin access anyway.18:19
torgomaticgholt: true, but I wonder if they work at all18:20
torgomaticif it's my account, my manifest, and my segments, I should be able to make a large-object tempurl18:20
gholtIf we ever change that so non-account-admins can make tempurls, we'll have to fix that. Er, I mean, whoever does that work. :)18:20
*** mkollaro has joined #openstack-swift18:21
* torgomatic ∉ "we" :)18:21
*** mkollaro has quit IRC18:21
*** joeljwright has joined #openstack-swift18:55
*** shri has joined #openstack-swift18:55
*** byeager has joined #openstack-swift18:57
mjsegernotmyname: just wondering if you made it to the office yet as I doubt it's snowing like mad there like it is here  ;)19:03
*** joeljwright has quit IRC19:05
*** shri has quit IRC19:06
*** shri1 has joined #openstack-swift19:07
*** byeager_ has joined #openstack-swift19:07
*** shri1 has quit IRC19:08
*** mmcardle has quit IRC19:09
*** byeager has quit IRC19:10
cschwedemjseger: I'm back, thanks for putting getput to github, I'm now looking into it19:21
mjsegerok, great.  and thanks.  some real quick tips to get this going:19:21
mjsegerI always build a file that exports my credentials to ST_variable19:22
mjsegeronce exported, a simple command like this will write 10 1k objects to a container named c and objects named o19:22
mjseger./getput.py -cc -oo -n1 -s1k -tp19:22
mjsegeryou can vary things quite a lot and even run lots of parallel processes19:23
mjsegermy favorite swift is -s1k,2k which first does 1k operations than that does them again with 2k objects19:23
mjsegerjust give a holler if it doesn't work straight away19:24
cschwedemjseger: works out of the box, thanks!19:25
* cschwede now trying different swiftclient versions19:25
mjsegercschwede: good to hear.  lots more options when you're ready for them. such as spitting out individual transaction IDs so you can use it to dig through the logs if you need to19:26
mjsegerso for the record, if you run with 1.9 you should see 2k objects anywhere from 2 to 4 times slows.  if you run with 2.0.2 and request < 2.1.1, you should see similar ratios but slower.  if you run with requests 2.1.1 the 1k and 2k numbers are the same since nagel disabled, but they're still slower than with 1.919:29
mjsegerat least that's what I'm seeing19:29
*** mmcardle has joined #openstack-swift19:37
*** fbo is now known as fbo_away19:37
*** mmcardle1 has joined #openstack-swift19:39
*** mmcardle has quit IRC19:41
cschwedemjseger: what kind of test environment are you using? is that a production swift cluster or running in a local VM?19:42
mjsegeractually this is in a testing environment and I'm running on bare metal but I'm hitting our production servers19:43
mjsegerhave  you gotten any results worth sharing yet?19:44
cschwedemjseger: http://paste.openstack.org/show/66991/ -> 2.0.2 much better for PUT, 1.9.0 a little bit better for GET19:44
mjsegerreally!?!  that is a surpise as I saw 2.0.2 slower for both small and large objects19:45
cschwederunning in a local SAIO VM, cleared before both runs (ie no container/objects on the disks)19:45
cschwederepeated it three times, just to be sure19:45
mjsegerI wonder if ssl compression at your place is enabled by default.  try running again and add --nocomp because I think I head 2.0.2 disables compression by default and so if 1.9 doesn't that could explain some times19:47
cschwedemjseger: my local env is hitting the proxy server directly, ie no load balancer/ssl terminator in between and the proxy itself is running without SSL. Maybe that is the reason19:47
cschwedemjseger:  there is no ssl at all for my local VM19:47
mjsegerthere are a lot of variables19:47
mjsegerthe other piece is the compression19:47
mjsegeryou're also using a LOT of cpu compared to me.19:48
cschwedemjseger: most likely because I only assigned 1 VCPU to the VM19:48
cschwedeand everything is run in that VM19:48
mjsegerthe other thing that is interesting is your 1k and 2k PUT IOPS are about the same for both whereas mine if over 3 time faster with 1.919:48
mjsegeras someone asked my earlier, or was it you?, whether or not I was starting each test cleanly,  if you add --utc getput will append the current time to the name of the container assuring an empty/unique container19:50
cschwedemjseger: yepp, i was asking that19:52
mjseger;)19:52
mjsegercschwede: well this is certainly unsettling if you're getting that much better performance than me.  ;(19:55
mjsegerI'd've expected things to be similar19:55
cschwedemjseger: yes, but i think we need to find the reason for these differences. I'm adding a pound SSL terminator now...19:55
mjsegeryes, we do use poind19:56
*** joeljwright has joined #openstack-swift20:02
cschwedei needed to disable ssl cert verification (I'm only using a self-generated cert), but the results are nearly the same20:04
cschwedemjseger: maybe you could test also without cert verification?20:05
*** gyee has quit IRC20:05
cschwedemjseger: i changed line 541 and 550 in getput.py to "os_options=opts, ssl_compression=comp, insecure=True)"20:05
mjsegercschwede: how do I do that?20:05
mjseger;)20:06
mjsegerI think I can handle that20:06
*** joeljwright has quit IRC20:06
mjsegercschede: a little faster but still not as fast as 1.9.  btw - did you really mean line 550?  that's the connection for older versions of swiftclient that don't support connection.close()20:09
mjsegerI added that code in both connection calls20:09
mjsegerbtw, sounds like I need a new switch  ;)  --insecure20:10
*** joeljwright has joined #openstack-swift20:11
mjsegercschwede: here's a new switch for you (I love switches), "--ldist 2" it will report a latency histogram to 2 decimal places showing how many options of different durations there were20:13
mjsegerwhen I do 100 PUTs I see 11 in the 0.02 bucket, 71 in the 0.03 bucket, 14 in the 0.04 bucket and 4 in the 0.05 one20:14
cschwedei changed line 541 and 550 yes, because i was only looking where the connection is created ;-)20:14
mjsegersince you're going faster than me I'd expect higher counts in lower numbered buckets20:14
cschwedelets see20:16
*** joeljwright has quit IRC20:16
cschwedemjseger: http://paste.openstack.org/show/67006/20:23
mjsegercschwede: bingo - see how most of your operations are in the 0.01/0.02 seconds in the 2.0 case compare to 1.9?20:25
*** mmcardle1 has quit IRC20:25
*** mmcardle has joined #openstack-swift20:27
cschwedemjseger: yes, i see it, but 1.9.0 is still slower? put for 1.9.0 is in 0.04/0.05 range, and some get in 0.01 instead of 0.0020:27
mjsegerright, your puts are  slower than mine and I don;t know why20:28
mjsegermaybe I shoudl try this out on a VM tjat is closer to the production swift servers.  hang on...20:29
*** byeager_ has quit IRC20:30
mjsegercschewe: might be making progress, both the 1.9 and 2.0 times are the same, wiht the 1k PUTs being 3 times slower.  now I'll upgrade to request 2.2.1 and see if they equal out wiht nagel disabled20:43
mjsegercschede: hmm, that didn't help.  don't you installed reuests via a command like: sudo pip install requests-2.2.1.tar.gz ?20:45
mjsegerit says it successfully installed but I'm seeing 1K puts with iops of 20 and 2K puts with iops of 68!20:46
mjsegeroh wait, I didn't install python-swiftclient!  ;)20:46
mjsegerit was still at v1.5, talk abotu ancient  ;)20:47
mjsegerdamn, both 1k and 2k down to 12 IOPS with 2.020:48
mjsegersomething clearly wrong here20:48
mjsegercschwede: you're in europe, right?20:50
cschwedemjseger: yepp, in hamburg/germany20:51
*** shri has joined #openstack-swift20:52
mjsegerI'm wondering if we can table this until the morning (though it's only 4PM here in new england) and wait until my irish colleagues are awake and perhaps they can join in too as they know more about the configuration details20:52
mjsegerclearly this is something we want to get to the bottom of20:52
cschwedemjseger: sure, actually it is high time for me to close my laptop soon ;-)20:54
mjsegeras an aside if you still want to play a little with getput just to see what it can do, if you include the switch --latexc number, it will report any individual operations that exceed that latency ( specified as a float) along with the transaction IDs and container/object names20:54
mjsegerok great, and thanks for your attention.  we'll talk again tomorrow20:54
cschwedemjseger: looks like that tool is really sophisticated. I will play with it more tomorrow. thanks and see you tomorrow!20:55
cschwedemjseger: ... and btw: tomorrow at 7pm utc is the swift meeting, if you like to join :)20:56
mjsegeractually as they say, "you ain't see nothing yet".  what until you check out gpsuite!  I've has as many as 2048 processes accessing swift in parallel!20:56
*** byeager has joined #openstack-swift21:00
*** mvenesio has quit IRC21:06
*** gholt has quit IRC21:07
*** gholt has joined #openstack-swift21:08
*** ChanServ sets mode: +v gholt21:08
*** byeager has quit IRC21:08
*** joeljwright has joined #openstack-swift21:12
*** joeljwright has quit IRC21:17
*** gyee has joined #openstack-swift21:49
*** gyee has quit IRC21:51
*** gyee has joined #openstack-swift21:51
*** byeager has joined #openstack-swift21:53
*** shri has quit IRC21:53
*** mmcardle has quit IRC22:09
*** Trixboxer has quit IRC22:12
*** joeljwright has joined #openstack-swift22:13
*** joeljwright has quit IRC22:18
*** joeljwright has joined #openstack-swift22:31
openstackgerritpaul luse proposed a change to openstack/swift: Add Storage Policy Support to Account HEAD  https://review.openstack.org/7374722:48
creihtso I have done some initial testing22:49
*** shri has joined #openstack-swift22:49
creihtand swiftclient 2.0 is about 5-10% slower than 1.9 for smaller objects22:49
creihtand that is all I have tested so far22:49
creihtoh and that's without ssl22:52
creihtbut that also begs to question, at what point do we really consider too slow?22:52
*** zaitcev has joined #openstack-swift22:55
*** ChanServ sets mode: +v zaitcev22:55
creihtfor larger files there is little to no difference between the two22:56
portanteand do we consider python-swiftclient a tool that has a performance requirement?22:59
notmynameto me swiftclient has never been the thing to use for performance. not to say that it should be slow, but you'd probably go faster if you write your own wrapper23:01
creihtnotmyname: well yeah, but if it were say %50 slower, then I might consider that a problem :)23:02
notmynameagreed :-)23:03
notmynameof course, a 5-10% drop in each release adds up ;-)23:03
creihtyes23:03
*** rturk-aw` has joined #openstack-swift23:09
*** krtaylor has quit IRC23:16
*** bsdkurt has quit IRC23:16
*** rturk-away has quit IRC23:16
*** openstackgerrit has quit IRC23:16
*** portante has quit IRC23:16
*** Anju has quit IRC23:16
*** jokke_ has quit IRC23:16
*** dmsimard has quit IRC23:17
*** joeljwright has quit IRC23:18
*** krtaylor has joined #openstack-swift23:18
*** bsdkurt has joined #openstack-swift23:18
*** openstackgerrit has joined #openstack-swift23:18
*** Anju has joined #openstack-swift23:18
*** jokke_ has joined #openstack-swift23:18
*** portante has joined #openstack-swift23:18
*** ChanServ sets mode: +v portante23:18
*** Midnightmyth has quit IRC23:20
*** byeager has quit IRC23:20
*** shri1 has joined #openstack-swift23:22
*** shri has quit IRC23:25
mjsegernotmyname: sorry, I've been clearing my driveway of a lot of snow.  from my perspective, I though if I wanted to talk to swift via python the recommended method is using swiftclient, and so that's why I used it with getput.  are people backing away from that statement?23:27
mjsegeras for the performance difference, I saw a much bigger drop than 10% for small object and also a drop that might've been around 10% for large ones.  but since I'm the only one who saw that perhaps it's my configuration and not swiftclient23:28
mjsegerthe plan it to continue the discussion with cschwede in the morning  and see if we can identify the problem23:29
*** tongli has quit IRC23:33
*** mmcardle has joined #openstack-swift23:39
*** byeager has joined #openstack-swift23:41
*** byeager has quit IRC23:44
*** mmcardle has quit IRC23:56

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!