allegro / allegro/bigcache

BigCache is logging allocations it should not

Offen
#363 4 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
bug
Vorherrschende Sprache
Go
Sterne
8.2k
Forks
614
Ø Merge
5 T. 12 Std.
Gemergte PRs (30 T.)
1

Beschreibung

**What is the issue you are having?**
I have deployed the version 3.0.2 and I thought this issue: https://github.com/allegro/bigcache/issues/117 meant it was solved.
I have a constant flow of the below messages on my logs.

Can you help me understand how to fix this?

**What is BigCache doing that it shouldn't?**
It should not log this every few milliseconds :
```
2023/06/05 02:37:51 Allocated new queue in 92.911µs; Capacity: 614400
2023/06/05 02:37:50 Allocated new queue in 81.841µs; Capacity: 614400
...
```

**Minimal, Complete, and Verifiable Example**

When asking a question about a problem caused by your code, you will get much better answers if you provide code we can use to reproduce the problem. That code should be...

* ...Minimal – Use as little code as possible that still produces the same problem
* ...Complete – Provide all parts needed to reproduce the problem
* ...Verifiable – Test the code you're about to provide to make sure it reproduces the problem

For more information on how to provide an MCVE, please see the [Stack Overflow documentation](https://stackoverflow.com/help/mcve).

**Environment:**
- Version (git sha or release): NA
- OS (e.g. from `/etc/os-release` or winver.exe): alpine3.15
- go version: golang:1.17.9

Beitragsleitfaden

Für dieses Repository ist kein Beitragsleitfaden indexiert

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.