spikes, sorry fore the typo.
Ali
On 4/3/21 7:50 PM, Ali Alhaidary wrote:
Thanks, we have not seen any spices in CPU during last week as well,
keeping in mind that the usage was 50% less due to holidays. We will
keep monitoring...
Ali
On 4/3/21 7:37 PM, Maxim Solodovnik wrote:
My unit test demonstrates no serious degradation caused by bean
injections
Not sure what else can it be :(
On Sat, 27 Mar 2021 at 10:09, Ali Alhaidary
<ali.alhaid...@the5stars.org <mailto:ali.alhaid...@the5stars.org>> wrote:
Our production server is less than 25% concurrent users of your
test :-)
Ali
On 3/27/21 4:15 AM, Maxim Solodovnik wrote:
I'll try to write some synthetic tests (not sure when :( )
(GSoC is coming and require some time :((( )
injection mechanism can be fixed :)
On Sat, 27 Mar 2021 at 05:40, seba.wag...@gmail.com
<mailto:seba.wag...@gmail.com> <seba.wag...@gmail.com
<mailto:seba.wag...@gmail.com>> wrote:
My last round of performance tests, I think was ~3 weeks
ago. It was doing fine with 400 concurrent users. No
performance impact on OpenMeetings itself.
If this Bean Injection would do anything? I'm not sure. I
can't imagine that.
There is some evidence that this has been a performance
issue before:
https://github.com/bironran/spring_issues_generic_provider
<https://github.com/bironran/spring_issues_generic_provider>
But I'm not sure if we are using the same mechanism as
described in the above issue. We are using @Inject. The
example is around usage of Provider pattern. Not sure if it
is the same mechanism at the core.
I can run another test with a smaller number of users and
compare the metrics over the next few days.
Thanks
Seb
Sebastian Wagner
Director Arrakeen Solutions, OM-Hosting.com
http://arrakeen-solutions.co.nz/
<http://arrakeen-solutions.co.nz/>
https://om-hosting.com <https://om-hosting.com> - Cloud &
Server Hosting for HTML5 Video-Conferencing OpenMeetings
<https://www.youracclaim.com/badges/da4e8828-743d-4968-af6f-49033f10d60a/public_url><https://www.youracclaim.com/badges/b7e709c6-aa87-4b02-9faf-099038475e36/public_url>
On Fri, 26 Mar 2021 at 20:35, Ali Alhaidary
<ali.alhaid...@the5stars.org
<mailto:ali.alhaid...@the5stars.org>> wrote:
can you reproduce it on your servers and take a look on
performance ?
Ali
On 3/26/21 3:44 AM, Maxim Solodovnik wrote:
> maybe because of this one:
>
https://issues.apache.org/jira/browse/OPENMEETINGS-2588
<https://issues.apache.org/jira/browse/OPENMEETINGS-2588>
....
>
> @Seba maybe you can check with your performance scripts?
>
> On Fri, 26 Mar 2021 at 00:07, Ali Alhaidary
<ali.alhaid...@the5stars.org
<mailto:ali.alhaid...@the5stars.org>> wrote:
>> May be two week ago ...
>>
>> Ali
>>
>> On 3/25/21 7:59 PM, Maxim Solodovnik wrote:
>>> or maybe you can remember the date when this build
was created?
>>>
>>> On Thu, 25 Mar 2021 at 18:47, Maxim Solodovnik
<solomax...@gmail.com <mailto:solomax...@gmail.com>> wrote:
>>>> well
>>>>
>>>> as you can see
https://ci-builds.apache.org/job/OpenMeetings/job/openmeetings/
<https://ci-builds.apache.org/job/OpenMeetings/job/openmeetings/>
>>>> there is no build #262 anymore :(
>>>> so I can't check what was changed :(
>>>>
>>>> any chance you have this build saved locally?
>>>> if so open
webapps/openmeetings/WEB-INF/lib/openmeetings-util-6.1.0-SNAPSHOT.jar
>>>> with archiver
>>>> check /org/apache/openmeetings/util/version.properties
>>>> send me `revision=8c63465` :)))
>>>>
>>>> On Thu, 25 Mar 2021 at 18:42, Ali Alhaidary
<ali.alhaid...@the5stars.org
<mailto:ali.alhaid...@the5stars.org>> wrote:
>>>>> Production server is at the latest snapshot
(build#285), we have been
>>>>> noticing this since around build#262 until now
>>>>>
>>>>> Ali
>>>>>
>>>>> On 3/25/21 2:32 PM, Maxim Solodovnik wrote:
>>>>>> build#262 ...
>>>>>> what date does it have?
>>>>>> or maybe you can share the hash from OM -> About ?
>>>>>>
>>>>>> On Thu, 25 Mar 2021 at 18:28, Ali Alhaidary
<ali.alhaid...@the5stars.org
<mailto:ali.alhaid...@the5stars.org>> wrote:
>>>>>>> Hi,
>>>>>>>
>>>>>>> As of after build#262, 6.1.0 snapshot, we
noticed an increase of around
>>>>>>> 30% in CPU and RAM usage.
>>>>>>>
>>>>>>> Our production server used to be running 50% of
ram and CPU, however,
>>>>>>> now, sometimes CPU goes up to 90%. The
environment did change, that is 5
>>>>>>> rooms, 7-12 members in a room audio only.
>>>>>>>
>>>>
>>>> --
>>>> Best regards,
>>>> Maxim
>>>
>
>
--
Best regards,
Maxim
--
Best regards,
Maxim
