Bug 762377 (GLUSTER-645) - Determine best ratio wherein distribute is truly deterministic
Summary: Determine best ratio wherein distribute is truly deterministic
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-645
Product: GlusterFS
Classification: Community
Component: distribute
Version: 2.0.9
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Harshavardhana
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-19 12:28 UTC by Chida
Modified: 2015-03-23 01:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Chida 2010-02-19 12:28:23 UTC

Comment 1 Harshavardhana 2010-02-22 06:04:18 UTC
This ticket is to find total number of servers v/s total number of files required to reach deterministic file hashing. 

As example we have seen with 

4096 thread runs of mpi_io over a 24server setup leads to file hashing of large number of files to same node perhaps in 400's rather than 150-170 against each server. 

Whereas 8192 threads leads us to 330-350 thread ratio per server, which is perfect. 

Much research is required to understand how well with lesser and larger files we can reach deterministic hashing.

Comment 2 Shehjar Tikoo 2010-03-02 07:58:38 UTC
Please reopen this in the req bugzilla


Note You need to log in before you can comment on or make changes to this bug.