Asking about Gluster Performance Factors

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Title: Samsung Enterprise Portal mySingle

 

May 16, 2012

 

Dear Gluster Dev Team :

 

I'm Ethan, Assistant engineer in Samsung electronics. Reviewing your paper, I have some questions of performance factors in gluster.

 

First, what does it mean the option "performance.cache-*"? Does it mean read cache? If does, what's difference between the options "prformance.cache-max-file-size" and "performance.cache-size" ?

I read your another paper("performance in a gluster system, versions 3.1.x") and it says as below on Page 12,

(Gluster Native protocol does not implement write caching, as we believe that the modest performance improvements from rite caching do not justify the risk of cache coherency issues.)

 

Second, how much is the read throughput improved as configuring 2-way replication? we need any statistics or something like that.

("performance in a gluster system, versions 3.1.x") and it says as below on Page 12,

(However, read throughput is generally improved by replication, as reads can be delivered from either storage node)

 

I would ask you to return ASAP.

 

 

Sincerely yours,

 

 

 

Ethan Eunjun Park

 

Assistant Engineer,

Solution Development Team, Media Solution Center

416, Maetan 3-dong, Yeongtong-gu, Suwon-si, Gyeonggi-do 443-742, Korea

Mobile : 010-8609-9532

E-mail : ej1515.park@xxxxxxxxxxx

http://www.samsung.com/sec

 

 


[Index of Archives]     [Gluster Users]     [Ceph Users]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux