🎄 Happy Holidays! 🥳

Most of Solace is closed December 24–January 1 so our employees can spend time with their families. We will re-open Thursday, January 2, 2024. Please expect slower response times during this period and open a support ticket for anything needing immediate assistance.

Happy Holidays!

Please note: most of Solace is closed December 25–January 2, and will re-open Tuesday, January 3, 2023.

Slow Subscriber

Abu
Abu Member Posts: 13 ✭
in General Discussions #1

Hi,
I want to identify slow subscriber client in my sandbox environment. This is to mock or test when a client is marked as a slow consumer. Currently our slow subscriber panel in Grafana shows all clients as normal (i.e. 0 = not slow subscriber). Can anyone please suggest how this can be replicated in test environment ?
Maybe one option could be if we have message rate option in sdkperf where we can forcefully slow the consumer while publishing messages at much higher rate ?
Thanks!

Tagged:

Comments

  • nram
    nram Member, Employee Posts: 80 Solace Employee
    #2

    Hi @Abu , You can try sdkperf with "-sd 1000 -sdc -1” flags. If you are using sdkperf-java.sh, also consider using -cor arg.

  • Abu
    Abu Member Posts: 13 ✭
    #3

    Hi,
    Thanks for sharing those as -sd and -sdc looks promising options. However, I am not sure where I could find examples as I am unable to find them under : https://docs.solace.com/SDKPerf/Command-Line-Options.htm
    Could you please share references/examples/Soldocs ?

  • nram
    nram Member, Employee Posts: 80 Solace Employee
    edited March 2021 #4

    Hi @Abu , Here are sample commands: Pl tune per your requirement.

    Sample subscriber:
    Subscribe to test-queue with delayed ack. assumes test/topic is subscribed on to test-queue.

    ./sdkperf_java.sh -cip tcp://myvpn.messaging.solace.cloud:55555 -cu test-user@myvpn -cp 'mypassword' -sql test-queue -sd 100 -sdc -1 -cor

    Sample publisher:
    Publish 1K size message @ 1000/sec to test/topic

    ./sdkperf_java.sh -cip tcp://myvpn.messaging.solace.cloud:55555 -cu test-user@myvpn -cp 'mypassword' -ptl test/topic -mn 10000 -mr 1000 -msx 1024

  • Abu
    Abu Member Posts: 13 ✭
    #5

    Hi @nram , thank you for making it easier but this is the outcome:
    I published the messages at the rate and size you mentioned while my consumer was running on the other console.
    I observed that the messages were still being consumed at a very slow rate BUT that does not still qualifies to flag it as a "slow subscriber" in our Grafana Panel which has the query using the function "solace_client_slow_subscriber" . Also noticed when I run the following it consumes but intermittently and really slowly.
    $ ./sdkperf_java.sh -cip tcps://myvpn.messaging.solace.cloud:52444 -cu test-user@myvpn -cp 'password' -sql test-queue -sd 10000 -sdc -1 -cor
    Can you please suggest how can we stress the consumer (maybe more) to raise a flag "slow subscriber" for the client ?

  • nram
    nram Member, Employee Posts: 80 Solace Employee
    #6

    I believe its a function of the publishing rate, consumption rate, and duration of the test. @Aaron , do you have thoughts?

  • Abu
    Abu Member Posts: 13 ✭
    #7

    good news, finally I was able to replicate the "slow subscriber" function in action in my test env. It took some time (~15mins) with the subscriber "sdkperf_java" left running. @nram: thank you for the command samples however it would be nice to have access to the document for sdkperf_java to identify each options more appropriately.

  • nram
    nram Member, Employee Posts: 80 Solace Employee
    #8

    Glad you were able to test this out @Abu. IN addition to sdkperf docs available online, best option is to run sdkperf_java.sh -hm (more help) and inspect the output.

  • Aaron
    Aaron Member, Administrator, Moderator, Employee Posts: 644 admin
    #9

    Late to the game on this one, team. Sorry! Sounds like you're sorted though. 👍 To make your consumer slower faster, try increasing the message rate... hopefully wouldn't take 15 minutes in the future.

    And yes, I use the -hm option all the time. Best thing is, you don't have to use it alone: you can have all your other params: -cip -cu -ptl -mn -mr -msa etc., and then if you forgot how to do one thing, just add on -hm | grep <blah> and look for a feature or name of something in the giant help screen that's displayed.

Categories

This Month's Leaders

This Week's Leaders