Perfomance decrease in `DEBUG` logging level

Describe the bug When logging is set to DEBUG:

import logging
logging.getLogger().setLevel(logging.DEBUG)

then perfomance is greatly decrease and more than 80% of time is spent on logging.

To Reproduce Steps to reproduce the behavior:

• download las file big enough to feel the problem
• set log level to DEBUG:

import logging
logging.getLogger().setLevel(logging.DEBUG)

• collect data:

import cProfile
cProfile.run("las=lasio.read(r'c:\Users\username\Downloads\A_Kerbel.las')", "c:/tmp/las.prof")

• install tuna to display results:

pip install tuna

• display results:

python -m tuna c:/tmp/las.prof

• now you can see that about 80% is spent on debug. Is that ok?

Expected behavior I guess debug should take less than 80% of the time

Software versions (please complete the following information):

• Python 3.6.7 (default, Jun 26 2021, 18:30:45) [MSC v.1929 64 bit (AMD64)] on win32
• lasio version 0.29

Additional context Please see my topic dedicated to this problem. Here you can simply find all the information needed to understand the problem.

P.S. I’m not much expert in profiling and I only have little experience of working in python so I appologize if I explained some staff cumbersome

[kerim371]

@kinverarity1 thank you very much, it seems now it works fast as expected. To test it I did:

pip install git+https://github.com/kinverarity1/lasio.git

then inside my Slicer’s python shell (wich sets DEBUG log level):

import lasio
las=lasio.read(r'd:d\A_Kerbel.las')

less than a second has past to perform these two lines of code

[kinverarity1]

@kerim371 if you are able to test the master branch of lasio to see if it helps that would be appreciated. I have moved the offending logger call to a custom level which is set below the standard DEBUG level.