+ Reply to Thread
Results 1 to 2 of 2

Thread: symping- testing tool

  1. #1
    satish is offline Junior Member
    Join Date
    May 21st, 2009
    Posts
    4
    Downloads
    0
    Uploads
    0

    Default symping- testing tool

    Hi,
    This is with reference to
    "Symping-testing tool" in administrative and config tips.


    Kindly let me know if below inference is correct.

    case1
    Set the input message size to 100 bytes
    Set the output message size to 100 bytes
    Set the task processing time to 100 milliseconds
    Set the number of tasks per test run to 4000

    case2
    Set the input message size to 10000 bytes
    Set the output message size to 10000 bytes
    Set the task processing time to 10 seconds
    Set the number of tasks per test run to 40

    So as per your analysis case2 is faster than case1. This implies lesser number of tasks, lesser SI's, more message data sent and faster throughput. But doesn't this indicate more data has to be serialized and transferred through network?

    Are tasks threadsafe and independent of each other processing? - But they execute in same jvm.

    How do nodes in cluster discover and communicate with each other? UDP or tcp?

    Ideally only taskid's, serviceid's should be sent which will reduce network latency and message data is taken from in memory grid. Am I right?

    Thanks

  2. #2
    Ajith's Avatar
    Ajith is offline Symphony DE Moderator
    Join Date
    February 28th, 2008
    Location
    Markham, Ontario
    Posts
    104
    Blog Entries
    2
    Downloads
    10
    Uploads
    0

    Default

    Quote Originally Posted by satish View Post
    Hi,
    This is with reference to
    "Symping-testing tool" in administrative and config tips.


    Kindly let me know if below inference is correct.

    case1
    Set the input message size to 100 bytes
    Set the output message size to 100 bytes
    Set the task processing time to 100 milliseconds
    Set the number of tasks per test run to 4000

    case2
    Set the input message size to 10000 bytes
    Set the output message size to 10000 bytes
    Set the task processing time to 10 seconds
    Set the number of tasks per test run to 40

    So as per your analysis case2 is faster than case1. This implies lesser number of tasks, lesser SI's, more message data sent and faster throughput. But doesn't this indicate more data has to be serialized and transferred through network?

    Are tasks threadsafe and independent of each other processing? - But they execute in same jvm.

    How do nodes in cluster discover and communicate with each other? UDP or tcp?

    Ideally only taskid's, serviceid's should be sent which will reduce network latency and message data is taken from in memory grid. Am I right?

    Thanks
    Hi Satish,

    The second case involves fewer messages, so it will require less management overhead to transfer through the system.

    The tasks are threadsafe since they the service instances only run one task at a time / instance.

    Sym DE discovers using the vem_resources.conf file and communications is done through TCP.

    Sym DE doesn't use a data grid. All task data is transferred thru the system.

    - Ajith

+ Reply to Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts