[prev in list] [next in list] [prev in thread] [next in thread]
List: mifos-developer
Subject: Re: [Mifos-developer] Announcing a Scalability and Performance benchmark test
From: Muellners ApS <ankit () muellners ! org>
Date: 2021-10-17 10:36:48
Message-ID: CAOxd=AyFTEcSjba=bEJ18qxg+mhofne4z+=soufagvhf3r2sPQ () mail ! gmail ! com
[Download RAW message or body]
[Attachment #2 (multipart/alternative)]
I am bringing back this thread from *July 2020*, observing the Fineract 1.x
roadmapping discussion
<https://lists.apache.org/list.html?dev@fineract.apache.org> taking place
now in *Oct 2021*. My goal here is to recommend that we should pick up on a
non-partisan Performance and Scalability test from here. This subject is
progressively significant to the project and to the roadmapping discussion
itself as depicted below:
"Thirdly, going back to Fineract 1.x, one of the key issues is around the
scalability and performance of the platform. A number of participants
mentioned that fineract 1.x is starting to be used in increasingly
large-scale scenarios."
>> Yes and designing an updated test is much required.
I have conducted two of them in the last 1 year(one with 1.x+Mifos app and
other only with 1.x APIs) on a pre production instance (since this July
2020). Would be great to add those results to the project
documentation.(above release 1.5)
"Alternatively, outside of the project, Community members may be able to
get results and share them here. That may be the easier path to establish
some baselines. We have some old data, but nothing from release 1.5."
>> I am now beginning to schedule an updated "Performance & Scalability
Benchmark test" on Fineract 1.x.
It would be great to add findings from all three of these tests. These
tests themselves speak for reinforcing stability of Fineract 1.x
implementations for mid scale financial services providers.
# Community members should also conduct these tests on other infra. IBM
Cloud services and AWS were used primarily for the above two tests.
# Performance & Scalability tests tell us a lot including exhibiting
security vulnerabilities of the project. For future recommendation, a smart
objective is to create replicable IT tests and Performance/Scalability
Benchmark tests both on Apache Infra so that these can be quarterly
reported.
# Now the test documentation is released by Muellners Foundation not me,
which has released some information in public domain attaching a Creative
Commons License with it's OSS Usage and Delivery Policy
<https://docs.muellners.info/open-source-policies/open-source-usage-and-delivery-policies>
.
I cannot help but cite this non for profit as this is their Intellectual
Property (released with an open source license) to share here, not mine.
It's like quoting a book, basic internet literacy.
Thanks
On Sun, Aug 2, 2020 at 3:46 PM Giorgio Zoppi <giorgio.zoppi@gmail.com>
wrote:
> Hello,
> in the case of CN would be interesting see the "collateral damage" i mean
> fail over under stress conditions.
> The point of the stress benchmark is using something that is faster than
> JVM/CLR to create requests in brief amount of time: i mean a multithread
> native client written in C or Go that in case of the CN
> automates all flow. We can work on the specification.
> BR,
> Giorgio.
>
> --
> Life is a chess game - Anonymous.
>
--
Ankit
Managing Partner
Muellners ApS, Denmark
Impressum- Muellners ® Inc; Copenhagen, Denmark CVR: 41548304;
New Delhi, India CIN: U72900DL2019PTC344870; Foundation EU CVR:41008407
This mail is governed by Muellners ® IT policy.
The information contained in this e-mail and any accompanying documents may
contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if
this message has been addressed to you in error, please immediately alert
the sender by reply e-mail and then delete this message, including any
attachments. Any dissemination, distribution or other use of the contents
of this message by anyone other than the intended recipient is strictly
prohibited. All messages sent to and from this e-mail address may be
monitored as permitted by applicable law and regulations to ensure
compliance with our internal policies and to protect our business. E-mails
are not secure and cannot be guaranteed to be error free as they can be
intercepted, amended, lost or destroyed, or contain viruses. You are deemed
to have accepted these risks if you communicate with us by e-mail.
[Attachment #5 (text/html)]
<div dir="ltr">I am bringing back this thread from <b>July 2020</b>, observing the <a \
href="https://lists.apache.org/list.html?dev@fineract.apache.org" \
target="_blank">Fineract 1.x roadmapping discussion</a> taking place now in <b>Oct \
2021</b>. My goal here is to recommend that we should pick up on a non-partisan \
Performance and Scalability test from here. This subject is progressively significant \
to the project and to the roadmapping discussion itself as depicted \
below:<div><br></div><div>"Thirdly, going back to Fineract 1.x, one of the key \
issues is around the scalability and performance of the platform. A number of \
participants mentioned that fineract 1.x is starting to be used in increasingly \
large-scale scenarios."</div><div>>> Yes and designing an updated test is \
much required. </div><div>I have conducted two of them in the last 1 year(one with \
1.x+Mifos app and other only with 1.x APIs) on a pre production instance (since this \
July 2020). Would be great to add those results to the project documentation.(above \
release 1.5)</div><div><br></div><div>"Alternatively, outside of the project, \
Community members may be able to get results and share them here. That may be the \
easier path to establish some baselines. We have some old data, but nothing from \
release 1.5."</div><div>>> I am now beginning to schedule an updated \
"Performance & Scalability Benchmark test" on Fineract 1.x. \
</div><div>It would be great to add findings from all three of these tests. These \
tests themselves speak for reinforcing stability of Fineract 1.x implementations for \
mid scale financial services providers.</div><div><br></div><div># Community members \
should also conduct these tests on other infra. IBM Cloud services and AWS were used \
primarily for the above two tests. </div><div><br></div><div># Performance & \
Scalability tests tell us a lot including exhibiting security vulnerabilities of the \
project. For future recommendation, a smart objective is to create replicable IT \
tests and Performance/Scalability Benchmark tests both on Apache Infra so that these \
can be quarterly reported. <br></div><div><div><br></div><div># Now the test \
documentation is released by Muellners Foundation not me, which has released some \
information in public domain attaching a Creative Commons License with it's <a \
href="https://docs.muellners.info/open-source-policies/open-source-usage-and-delivery-policies" \
target="_blank">OSS Usage and Delivery Policy</a>. </div><div>I cannot help but cite \
this non for profit as this is their Intellectual Property (released with an open \
source license) to share here, not mine. It's like quoting a book, basic internet \
literacy.</div></div><div><div><br></div></div><div>Thanks</div><div><br></div><div><div><br></div><br><div \
class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Aug 2, 2020 at 3:46 PM \
Giorgio Zoppi <<a href="mailto:giorgio.zoppi@gmail.com" \
target="_blank">giorgio.zoppi@gmail.com</a>> wrote:<br></div><blockquote \
class="gmail_quote" style="margin:0px 0px 0px \
0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div \
dir="ltr"><div dir="ltr"><div>Hello,</div><div>in the case of CN would be interesting \
see the "collateral damage" i mean fail over under stress conditions. \
<br></div><div>The point of the stress benchmark is using something that is faster \
than JVM/CLR to create requests in brief amount of time: i mean a multithread native \
client written in C or Go that in case of the CN</div><div>automates all flow. We can \
work on the specification.<br></div></div><div>BR,</div><div>Giorgio.<br></div><div><br>-- \
<br><div dir="ltr"><div dir="ltr">Life is a chess game - \
Anonymous.<br></div></div></div></div> </blockquote></div><br \
clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><span \
style="color:rgb(0,123,53);font-family:"Helvetica \
Neue",Helvetica,Arial,sans-serif;font-size:15px">Ankit</span><div><span \
style="color:rgb(0,123,53);font-family:"Helvetica \
Neue",Helvetica,Arial,sans-serif;font-size:15px">Managing Partner \
</span><div><span style="color:rgb(0,123,53);font-family:"Helvetica \
Neue",Helvetica,Arial,sans-serif;font-size:15px">Muellners ApS, \
Denmark</span><div><div style="color:rgb(0,0,0)"><span \
style="color:rgb(102,102,102);font-family:"Open \
Sans",Helvetica,Arial,sans-serif;font-size:14px"><br></span></div><div \
style="color:rgb(0,0,0)"><span style="color:rgb(102,102,102);font-family:"Open \
Sans",Helvetica,Arial,sans-serif;font-size:14px">Impressum- Muellners ® Inc; \
Copenhagen, Denmark CVR: </span><span \
style="color:rgb(102,102,102);font-family:"Open \
Sans",Helvetica,Arial,sans-serif;font-size:14px">41548304;</span></div><div \
style="color:rgb(0,0,0)"><span style="color:rgb(102,102,102);font-family:"Open \
Sans",Helvetica,Arial,sans-serif;font-size:14px">New Delhi, India CIN: \
</span><span style="color:rgb(102,102,102);font-family:"Open \
Sans",Helvetica,Arial,sans-serif;font-size:14px">U72900DL2019PTC344870; \
Foundation EU CVR:</span><span style="color:rgb(102,102,102);font-family:"Open \
Sans",Helvetica,Arial,sans-serif;font-size:14px">41008407</span><i><span \
style="font-family:"Helvetica Neue",Helvetica,Arial,sans-serif"> \
</span></i></div><span style="color:rgb(0,123,53);font-family:"Helvetica \
Neue",Helvetica,Arial,sans-serif;font-size:15px"> \
</span><br style="color:rgb(0,123,53);font-family:"Helvetica \
Neue",Helvetica,Arial,sans-serif;font-size:15px"><span \
style="color:rgb(0,123,53);font-family:"Helvetica \
Neue",Helvetica,Arial,sans-serif;font-size:15px">This mail is governed by \
Muellners ® IT policy.</span><br \
style="color:rgb(0,123,53);font-family:"Helvetica \
Neue",Helvetica,Arial,sans-serif;font-size:15px"><span \
style="color:rgb(0,123,53);font-family:"Helvetica \
Neue",Helvetica,Arial,sans-serif;font-size:15px">The information contained in \
this e-mail and any accompanying documents may contain information that is \
confidential or otherwise protected from disclosure. If you are not the intended \
recipient of this message, or if this message has been addressed to you in error, \
please immediately alert the sender by reply e-mail and then delete this message, \
including any attachments. Any dissemination, distribution or other use of the \
contents of this message by anyone other than the intended recipient is strictly \
prohibited. All messages sent to and from this e-mail address may be monitored as \
permitted by applicable law and regulations to ensure compliance with our internal \
policies and to protect our business. E-mails are not secure and cannot be guaranteed \
to be error free as they can be intercepted, amended, lost or destroyed, or contain \
viruses. You are deemed to have accepted these risks if you communicate with us by \
e-mail.</span><br></div></div></div></div></div></div></div>
Mifos-developer mailing list
mifos-developer@lists.sourceforge.net
Unsubscribe or change settings at:
https://lists.sourceforge.net/lists/listinfo/mifos-developer
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic