client: improve performance when watching log messages

[lzoubek]

Currently when watching of log messages is enabled, client POSTs every logRecord. My tests are producing a lot of log output and are running really slow when report-engine client is enabled.

Client should cache all logRecords and POST them at the end of test. Once I have some time, I'll try to implement it at least for java client

[jkandasa]

Libor, If we send log messages at the end logs will not be synced with test case.

On Report Engine everything refereed by local time (Report Engine Time) not remote time (test bed machine time), if we refer remote time, there is a high chance to get duplicated machine time.

So we might create a separate thread on client to communicate with server.

[lzoubek]

I thing separate thread will not resolve this issue either, because you'll have to keep some queue of log messages which will get delayed anyway (imagine that my test produces 200 log messages in 1 second, and a POST of 1 message to RE takes 300ms for example)

When I wrote python-client i HAD to send logTime within log message body, are you sure server uses Report Engine Time? If so, why does client have to send timestamp?

[jkandasa]

We are maintaining two time stamp. 1. Test Bed machine Time stamp (Where the client is running) 2. Report Engine Time stamp.(Where the report engine server is running). As I said earlier we are tracking all the logs with Report Engine time stamp. Currently we are not using client machine time stamp anywhere (except test suite details). In feature we may need to implement these time stamp for some reference. So that we are using two time stamps.