[Bug 41967] GlusterFS performance problems
https://bugzilla.wikimedia.org/show_bug.cgi?id=41967 Nemo changed: What|Removed |Added See Also||https://bugzilla.redhat.com ||/show_bug.cgi?id=822253 -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 41967] GlusterFS performance problems
https://bugzilla.wikimedia.org/show_bug.cgi?id=41967 Nemo changed: What|Removed |Added Depends on||36994 -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 41967] GlusterFS performance problems
https://bugzilla.wikimedia.org/show_bug.cgi?id=41967 Andre Klapper changed: What|Removed |Added Keywords|upstream|performance CC||aklap...@wikimedia.org --- Comment #1 from Andre Klapper 2012-11-10 15:01:07 UTC --- Assuming that Ubuntu 12.04 is used, this would be about glusterfs 3.2.5-1ubuntu1. RedHat ticket (which is in NEEDINFO state) recommends to get more info by: - # gluster volume profile VOLNAME start - Run workload - # gluster volume profile VOLNAME info (Repeat this a few times while the workload is present on the volume) - gluster volume profile VOLNAME stop (once the workload is complete) -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 41967] GlusterFS performance problems
https://bugzilla.wikimedia.org/show_bug.cgi?id=41967 --- Comment #2 from Ryan Lane 2012-11-16 20:46:03 UTC --- No. We're using the newest 3.3 from gluster debs. -- Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 41967] GlusterFS performance problems
https://bugzilla.wikimedia.org/show_bug.cgi?id=41967 Andre Klapper changed: What|Removed |Added Priority|Unprioritized |Low -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 41967] GlusterFS performance problems
https://bugzilla.wikimedia.org/show_bug.cgi?id=41967 Mike Wang changed: What|Removed |Added CC||fai...@wikimedia.org, ||mw...@wikimedia.org Component|General |Infrastructure Assignee|wikibugs-l@lists.wikimedia. |rlan...@gmail.com |org | -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 41967] GlusterFS performance problems
https://bugzilla.wikimedia.org/show_bug.cgi?id=41967 --- Comment #3 from Nemo --- Just to give an idea of how a bottleneck it is, even when issuing a zip -9 (slowest read/write possible with zip): 1801 root 20 0 444m 147m 1724 R 103 1.8 96:21.75 glusterfs 29831 nemobis 20 0 20640 11m 712 S 42 0.1 10:11.65 zip Is there a way to enable multithreading for glusterfs? Maybe multiple cores dedicated to it would manage to get enough data for a single CPU core to work on. -- You are receiving this mail because: You are watching all bug changes. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 41967] GlusterFS performance problems
https://bugzilla.wikimedia.org/show_bug.cgi?id=41967 Antoine "hashar" Musso changed: What|Removed |Added Status|NEW |RESOLVED CC||has...@free.fr Resolution|--- |WORKSFORME --- Comment #4 from Antoine "hashar" Musso --- The workaround is to either: - use /dev/vdb mounted on /mnt , with the drawback that if the instance dies, the data are loss. - migrate a given labs project to use the shared NFS server as has been done for toollabs and deployment-prep (beta cluster) Closing this bug since we have workarounds. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 41967] GlusterFS performance problems
https://bugzilla.wikimedia.org/show_bug.cgi?id=41967 Bug 41967 depends on bug 36994, which changed state. Bug 36994 Summary: [OPS] Add disk I/O to ganglia reports https://bugzilla.wikimedia.org/show_bug.cgi?id=36994 What|Removed |Added Status|PATCH_TO_REVIEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l