[Openais] scale part 3 - lcr-ize YKD
Steven Dake
sdake at redhat.com
Thu Apr 13 11:02:47 PDT 2006
On Thu, 2006-04-13 at 09:57 -0700, Mark Haverkamp wrote:
> On Thu, 2006-04-13 at 00:54 -0700, Steven Dake wrote:
> > The YKD dynamic linear voting algorithm for primary component selection
> > consumes 200MB of memory when the processor count is set to 128. As a
> > result, I am looking at a few things to reduce the memory footprint or
> > be able to turn off primary component selection for large scale clusters
> > that may not need primary component selection (aka virtual synchrony
> > filter).
> >
> > Immediately coming to mind are users of only the evs or cpg services, in
> > which case primary component selection is unnecessary.
> >
> > The first phase (patch attached) of this process is to turn the virtual
> > synchrony filter (vsf) into a loadable lcrso. The lcrso is named
> > vsf_ykd.lcrso.
> >
> > The next phase is to create configuration options which allow the
> > selection of the virtual synchrony filter lcrso to load. The default
> > will be ykd, but the user will also be able to select none (and avoid
> > the memory hogging for large scale clusters without vsf requirements).
> >
> > I also envision it would be likely for other primary component
> > algorithms that have lower availability but lesser memory requirements
> > to be produced (such as static voting).
> >
>
> Did you intend this patch line?
>
the evils of search and replace.
> Index: exec/Makefile
> ===================================================================
> --- exec/Makefile (revision 981)
> +++ exec/Makefile (working copy)
> @@ -22,7 +22,7 @@
> # ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE
> # LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
> # CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
>
>
> -# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
> +# SUBSTITUTE GOODS OR LCRICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
>
>
>
> # INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
> # CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
> # ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
>
More information about the Openais
mailing list