Is Gattling logging a bug/issue? how can i stop logging?

Hi I notice in the code that Gatling uses StrictLogging.

This means that the args will be evaluated even if we don’t use it.

Also this log call blocks on writing to the Console… this is massively impacting my Scenario which uses Pause() because pause logs at Info level (should it not be at trace or debug?)

Wouldn’t it be better to use Akka’s async logging to prevent blocking on write to the console? ( http://doc.akka.io/docs/akka/2.0/scala/logging.html ) ?

Also I’m currently testing using sbt-gatling, any idea how I can set LogLevel to Warn in the mean time so I can run my scenario without Pause spitting out so much log?

Cheers

Karl

Hi I notice in the code that Gatling uses StrictLogging.

This means that the args will be evaluated even if we don't use it.

Absolutely not. That just means that the logger is not lazy:
https://github.com/typesafehub/scalalogging/blob/master/scalalogging-slf4j/src/main/scala/com/typesafe/scalalogging/slf4j/Logging.scala#L55

Also this log call blocks on writing to the Console...

You can write to another appender, up to you.

this is massively impacting my Scenario which uses Pause() because pause
logs at Info level (should it not be at trace or debug?)

Maybe, we intend to change those logging levels. Anyway, you're the one who
enabled info. Gatling comes with warn.

Wouldn't it be better to use Akka's async logging to prevent blocking on
write to the console? (
http://doc.akka.io/docs/akka/2.0/scala/logging.html ) ?

IMHO, useless if you don't use logging intensively, which we don't.

Also I'm currently testing using sbt-gatling, any idea how I can set
LogLevel to Warn in the mean time so I can run my scenario without Pause
spitting out so much log?

You probably lack add a logback.xml or logback-test.xml file, right?

Thanks for the reply,

I really think that logging the fact that the Pause was passing should be at debug or lower in Pause.scala, after all when a user is creating(debugging) his own scenario he may want info comming off his own code, whith Pause logging at info level , my test really slowed down… try it. write a scenario where a number of users say 1000 do something then pause for 0.5 seconds, in a Loop(10) say… be at info logging level. time your test, then do the same without logging… massive difference eh!? I think that the core components should not spew anything out unless there is a problem.

PS you are right, I don’t have a logback.xml or logback-test.xml :slight_smile: thanks

Cheers

Karl

For the record, there’s already an open issue for cleaning up the logs: https://github.com/excilys/gatling/issues/1766