0

I get the warning

OpenBLAS WARNING - could not determine the L2 cache size on this system, assuming 256k

in the logs of the "LOGS" tab of the Cloud Function.

There is already a Q/A on this on Stack Overflow at AppEngine warning - OpenBLAS WARNING - could not determine the L2 cache size on this system, but it is not asked for a Google Cloud Function, only for the Google App Engine.

I wonder how I can get rid of this warning in a Google Cloud Function and whether I should care at all?

  • It is just a warning anyway and the quite heavy Cloud Function (with a lot of calculations + saving 50 MB csv, 700 MB needed RAM, 1 GB allocated, 540s timeout time) runs through anyway. Doing nothing can be an accepted answer.
  • Perhaps I can find the L2 cache size somewhere in the settings, which system is meant here?
questionto42standswithUkraine
  • 239
  • 1
  • 17

1 Answers1

1

The warning is just telling you that OpenBLAS which is a dependency of Pandas is not able to determine some settings of Cloud Function environment, most likely due to Cloud Function runs on virtualized environments. I suggest that you just ignore the warning as it is not an issue in Cloud Function.

tripleee
  • 1,324
  • 3
  • 14
  • 24
Catherine O
  • 153
  • 4
  • Makes sense since a CF is also just using a container. I do indeed `import pandas as pd` for the `pd.to_csv()` function :). Good catch. Perhaps a bit similar to running my own docker container locally to get [WARNING: Running pip as the 'root' user](https://stackoverflow.com/a/70586037/11154841) - which you can also just ignore. – questionto42standswithUkraine Feb 04 '22 at 17:48
  • 1
    Might perhaps get fixed with the help of [Compiling numpy with OpenBLAS integration](https://stackoverflow.com/questions/11443302/compiling-numpy-with-openblas-integration). I did not take the time to test this, but it might be possible to use OpenBLAS in a Cloud Function as well. – questionto42standswithUkraine Feb 04 '22 at 18:47