Forum Discussion

joysenthil's avatar
joysenthil
New Contributor
9 years ago

Ready API 1.6.0 crashes and fills all my memory if i simply open, close, save, open file of 55mb

after i moved from Soapui pro to Soapui NG PRO we have 80% memory usage and CPU usage 100% for files which has only 55mb Composite project.   As suggested by Customer care: In your Ready API insta...
solai's avatar
solai
New Contributor
9 years ago

Hi,

We too facing the same issue not able to open more projects in workspace, takes more for start-up and crashes often. Please provide solution for this as soon. 

 

Regards,

Solai

  • groovyguy's avatar
    groovyguy
    Champion Level 1
    9 years ago

    This happens to me multiple times a day, specifically more and more frequently when I am dealing with Test Projects that have 50,000+ properties that I have to manage. I generate these with a groovy script for every test run because the data needs to be unique. These projects are 40-50MB in size and absolutely cause SoapUI NG pro to choke. 

     

    The projects can take 3+ minutes to even open so with every crash I am losing time to work left and right. Add in the fact that I have four or five projects that are like this (and some I've had to split into MULTIPLE projects like this so they aren't even larger), it makes for an annoyance.


    SoapUI NG Pro chokes up on 100% cpu usage, and can get up to 8GB of ram (out of the 32GB I have.) There has to be something here that can be fixed.

    • nmrao's avatar
      nmrao
      Champion Level 3
      9 years ago
      50K + properties? Too much. Can you please elaborate the usecase, and if they all are required all the time?
      • groovyguy's avatar
        groovyguy
        Champion Level 1
        9 years ago

        The service I am testing has hundreds of required properties and hundreds more of optional pieces. Maybe I am approaching this the wrong way, but I am generating all of my data ahead of time so I can trace my data through the service since it adds, updates, deletes, etc. 


        Here's my path for testing using basic ideas of add/update methods for positive/NULL testing

        • Add - Positive
          • Figure out how many different variations are possible for a positive test case, usually figuring this out based on different combinations of choice-based elements. 
        • Add - NULL
          • This is where I see a lot of data necessary. I test every element individually (as long as it is schema compliant request) for elements that can be empty or completely omitted.
          • I test each element individually, and due to data unique constraints I have to have fresh properties every time. So if there are 150 possible schema-valid NULL test cases, that's 150 * 300 properties, so that's 45,000 properties I have to have ready to use

        Am I doing something wrong here? I am generating all data up front so I can make sure I have fresh data for every run through my test cases and in some cases the above numbers are doubled because I have to test similar cases for updating the data added with the add methods. 

         

        If this is wrong, what's the better way of doing this?