CPU issue when stress testing on broker for durable clients

Asked by Jianing Ren

Hi, Roger,

It is me again. I tested on new version of broker, and I still have the CPU issue.

This time I have make 300 simultaneous connections with clean session set to false, after disconnect, the broker is still using 8% of CPU, and it never decrease.

Then I have restarted the broker and tried 300 connections with clean session set to true this time under the same condition, the CPU usage went back to a really good stage after the clients disconnect.

So my question was what is difference and how broker dealing with durable and non-durable clients?

It seems like broker is doing something continuous even the durable-clients are offline.

By the way, I have tested on the new release, which is 1.3.5.

Thanks in advance.

Johnny Ren

Question information

Language:
English Edit question
Status:
Solved
For:
mosquitto Edit question
Assignee:
No assignee Edit question
Solved by:
Jianing Ren
Solved:
Last query:
Last reply:
Revision history for this message
Roger Light (roger.light) said :
#1

Like I said in my answer to your previous question, the big changes in
this are in the 1.4 branch. Could you try with that?

On Fri, Oct 24, 2014 at 5:06 AM, Jianing Ren
<email address hidden> wrote:
> Question #256127 on mosquitto changed:
> https://answers.launchpad.net/mosquitto/+question/256127
>
> Description changed to:
> Hi, Roger,
>
> It is me again. I tested on new version of broker, and I still have the
> CPU issue.
>
> This time I have make 300 simultaneous connections with clean session
> set to false, after disconnect, the broker is still using 8% of CPU, and
> it never decrease.
>
>
> Then I have restarted the broker and tried 300 connections with clean session set to true this time under the same condition, the CPU usage went back to a really good stage after the clients disconnect.
>
> So my question was what is difference and how broker dealing with
> durable and non-durable clients?
>
> It seems like broker is doing something continuous even the durable-
> clients are offline.
>
> By the way, I have tested on the new release, which is 1.3.5.
>
>
> Thanks in advance.
>
> Johnny Ren
>
> --
> You received this question notification because you are a member of
> Mosquitto PPA, which is an answer contact for mosquitto.

Revision history for this message
Jianing Ren (jianingr) said :
#2

Hi Roger,

Is 1.4 still in beta version? Or it is around the corner to be release? We want to try the version that is stable and safe enough as the our product is going to be release very soon.

Regards,
Johnny

Revision history for this message
Roger Light (roger.light) said :
#3

1.4 isn't yet released, so is subject to change. It is essentially
finished though and awaiting bug reports. I wrote this recently:
http://dev.eclipse.org/mhonarc/lists/mosquitto-dev/msg00264.html

Generally speaking the changes that would go into a 1.3.x (or 1.4.x)
bugfix release are incorrect functionality with relatively low numbers
of source code line changes. An overhaul of the internals like has
been started in 1.4 (and that should go some way to resolving what you
are seeing) is only appropriate for a feature release. My point is
that I appreciate your comments, but there will never be a 1.3.x
release that attempts to resolve it. Those changes are in 1.4 and will
be further improved on in 1.5.

Cheers,

Roger

On Mon, Oct 27, 2014 at 11:01 PM, Jianing Ren
<email address hidden> wrote:
> Question #256127 on mosquitto changed:
> https://answers.launchpad.net/mosquitto/+question/256127
>
> Status: Answered => Open
>
> Jianing Ren is still having a problem:
> Hi Roger,
>
> Is 1.4 still in beta version? Or it is around the corner to be release?
> We want to try the version that is stable and safe enough as the our
> product is going to be release very soon.
>
> Regards,
> Johnny
>
> --
> You received this question notification because you are a member of
> Mosquitto PPA, which is an answer contact for mosquitto.

Revision history for this message
Jianing Ren (jianingr) said :
#4

Thanks for your reply, Roger.

I will try 1.4 and let you know if any issues.

Thanks for your help.

Cheers,

Johnny