title: Log.d and impact on performance
body: <p>I'm not entirely sure about what I'm reading in the documentation. Is it ok to leave a bunch of log.d pieces of code scattered about, or should I comment them out so that they don't impact my app's performance.</p>
  
  <p>Thanks,</p>
  
  <p>I'm a little confused because if you read about the log object (<a href="http://developer.android.com/reference/android/util/Log.html" rel="noreferrer">documentation</a>) you see this:</p>
  
  <blockquote>
    <p>"The order in terms of verbosity, from least to most is ERROR, WARN,
    INFO, DEBUG, VERBOSE. Verbose should never be compiled into an
    application except during development. Debug logs are compiled in but
    stripped at runtime. Error, warning and info logs are always kept. "</p>
  </blockquote>
  
  <p>It almost sounded like it's ok to leave debug messages in there because they are "stripped." Anyway, thanks for the answers, I'll comment them out when I'm done. Not like I need them in there once the app is completed.</p>
  
  <p>Thanks</p>