[
https://issues.apache.org/jira/browse/ZOOKEEPER-440?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Hunt updated ZOOKEEPER-440:
-----------------------------------
Status: Open (was: Patch Available)
-1 on the current patch - it's too confusing, esp as the 3.1 graph is prior to
the 3.2 graph. really users care much more what the
current perf is, not necess how much it improved other than that it has
improved. ;-)
we should remove the pre-3.2 section and just replace the 3.1 section with the
3.2 new data. then add a paragraph at
the end of the section that summarizes how perf has improved (and howmuch) with
a link to the section in 3.1 for comparison. IMO anyway.
> update the performance documentation in forrest
> -----------------------------------------------
>
> Key: ZOOKEEPER-440
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-440
> Project: Zookeeper
> Issue Type: Task
> Components: documentation
> Reporter: Patrick Hunt
> Assignee: Benjamin Reed
> Fix For: 3.2.0
>
> Attachments: zkperfRW-3.2.jpg, ZOOKEEPER-440.patch
>
>
> Ben, it would be great if you could update the performance documentation in
> Forrest docs based on the 3.2 performance improvements.
> Specifically the scalling graphs (reads vs write load for various quorum
> sizes)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
