Forum Discussion

AndyHughes's avatar
AndyHughes
Regular Contributor
14 years ago

Table output doesn't display all rows

I have a load test and numerous table outputs attached. I have it set up to save the files to .csv in the .loadui directory.
The trouble is that the files don't always contain the results rows they should. Sometimes in a test of 5-6k requests there may be only a log of a few hundred lines??? where I may be expecting for instance perhaps 20,000 as I should have a row every 200ms.
In the last test I ran, there was only 1 line!!! It's seems really random..

10 Replies

  • Hello,

    Are all table log components in your project pointing to the same file and
    'Check to append selected file' option is checked?

    regards!
    Predrag
    SmartBear Software
  • AndyHughes's avatar
    AndyHughes
    Regular Contributor
    Hi Predrag,

    No I have various outputs, generating about 4 different files.
    I haven't got 'Check to append selected file' ticked as I do actually want a different file each time the test is run.
  • Hi,

    What is the structure of your project? Can you send sample project which demonstrates this or
    at least the screenshot.

    For this purpose I've created project with fixed rate generator, web runner and two table logs.
    I've set limit to 500 requests, and in files I got exactly 500 lines. The only problem I saw
    is when writing to the same file with append option checked, when some data is not written
    because of concurrent writing to the file.

    Are you running this in local or distributed mode?

    regards!
    Predrag
    SmartBear Software
  • AndyHughes's avatar
    AndyHughes
    Regular Contributor
    Hi,

    This is in local mode. but I'm using a ramp generator from 0 to 70req/sec over the course of 3 mins. Which ends up being about 6000 requests. I use a SOAPUI runner and the grid option as my data source in SOAPUI.

    But one table log I have (but not the only one with the problem) has a row generated every 200ms so thats 900 rows.
    But the main offender is the one which outputs the test case and all test steps of which there are 4 in the test case *6000 = 24k rows. A lot of rows appear to be missing and there is massive duplication in the ones that are saved. Some rows can be repeated 5-6 times.
  • DotTest37's avatar
    DotTest37
    Occasional Contributor
    Dear Andy,,,
    how did you get loadUI to write the CSV file?
    Im going crazy trying to do so,, I posted a question on the forum but nobody answered.

    I tested on Windows, Ubuntu and CentOS,, cannot get the Tablelog to actually create/write the output file.


    Thanks a lot in advanced.
    M.
  • Hi,

    Sorry for the late response.

    What do you have in "Max Rows in Table" file in General tab
    of table log settings dialog? Is it 1000?

    I was able to reproduce this, and I'm getting good results when
    total number of rows is lesser than 1000 but when is greater
    results are unpredictable. So, I suspect this setting is making
    trouble. Please, try to put greater number there (>24000) and see
    if it is working as expected. If we confirm this I will open an ticket.

    Note that in general not all component outputs will generate messages for
    each input request. Some will output one message per second so in the end
    you will have around 180 lines (3 minute test) and that's fine.

    regards!
    Predrag
    SmartBear Software
  • Hello,

    To make table log component write to csv file, open settings dialog
    and go to "Logging" tab. You need to check "Save logs?" check box and specify
    file path. Note that path is relative to loadUI home folder: ~/.loadui (for Win7
    this should be c:/users/<user>/.loadui). Path is always relative because
    when you have client running on one OS and agent on another absolute
    paths don't work.

    regards!
    Predrag
    SmartBear Software
  • AndyHughes's avatar
    AndyHughes
    Regular Contributor
    Hi Predrag, I'm not sure I understand your meaning. The table log is set to 1000 rows, after which it begins to throw rows away. This is fine, as I have it set to save to a .csv file which the documentation says will store all rows regardless of the 1000 setting. How will changing this setting affect the number of rows in the stored file. I will try it anyway. But I'm not sure if you are telling me to increase this number to 24000 or decrease it to less than 1000 as you said you had good performance when you reduced it???


    Ok, I've reduced it to 100 in each table log and this seems to make a difference. Although I've not had chance to ramp up the load properly yet as something else is wrong our end.
  • Hi,

    I'm talking about the potential bug. That setting certainly shouldn't affect
    export to csv file but for some reason it seams it does. So I just want to
    confirm that increasing that setting to some big number (greater than the
    expected number of lines that should be in the file in the end of the test)
    fixes this problem.

    regards!
    Predrag
    SmartBear Software