Thank you, Mike. I forgot to attach a sizing spreadsheet. I’ve now attached your spreadsheet to the article, and referenced it from the appropriate section in the article.
Thanks again, Edin On May 27, 2015, at 6:37 AM, Michael Stolz <[email protected]> wrote: > The linked article (Sizing+a+Geode+Cluster) refers to the sizing spreadsheet > several times, but doesn't point to where it can be found. > > Here is a copy of the one I use. Please find an appropriate place to post it. > > -- > Mike Stolz > Principal Technical Account Manager > Mobile: 631-835-4771 > > On Tue, May 26, 2015 at 5:07 PM, William Markito <[email protected]> wrote: > Hi Wes, feel free to create a JIRA for that if you would like but please > note that sizing should take into consideration the specifics of the > application which may not be easy captured in such estimating math > efforts... > > Some more information is already provided in our wiki at > https://cwiki.apache.org/confluence/display/GEODE/Sizing+a+Geode+Cluster > > > > On Tue, May 26, 2015 at 1:17 PM, Wes Williams <[email protected]> wrote: > > > I think another useful feature to access from the Geode web site is a > > system sizing spreadsheet. You plug in object size, # records, key size, # > > indexes, whether you have stats enabled, etc., etc. and it gives you the > > recommended # cache servers, cpu's. > > > > Where is the request backlog again? > > > > Thanks, > > > > *Wes Williams | Pivotal Sr. **Data Engineer* > > 781.606.0325 > > http://pivotal.io/big-data/pivotal-gemfire > > > > > > -- > > William Markito Oliveira > > -- For questions about Apache Geode, please write to > *[email protected] > <[email protected]>* > > <System Sizing Worksheet.xlsx>
