-
In one of our production clusters, the real memory usage of LRUQueryCache could be 10GB, almost 40 times larger than the estimated value (247MB) in `_nodes/stats` .
I have met this problem a few tim…
-
### System information
Type | Version/Name
--- | ---
Distribution Name | Proxmox VE (Debian GNU/Linux 12 (bookworm))
Distribution Version | proxmox-ve 8.2.4
Kernel Version | Linux erp…
-
> One should never rely on the number of bytes actually allocated corresponding to the number requested.
The number of bytes allocated is guaranteed to be the same (or more? I guess it's rounded up…
-
### What is the issue?
**Description:**
I encountered an issue where the **LLaMA 3.2 Vision 11b** model loads entirely in CPU RAM, without utilizing the GPU memory as expected. The issue occurs on m…
-
Hi, this is great news after 14 years!
i've tried the executable on an Epyc 7282 server 2019 with 128 GB RAM and on djvu files larger than ~ 25MB it gives for example:
Processing page 81 of 81
…
-
With #168 this is surprisingly close, besides all the things that GeoData does that xarray can't do.
But clearly missing are:
- [ ] Dask-like processing for larger-than-memory files. This should a…
-
Excellent work! I just wonder if there is any way to load the model in more than one GPU because even the 7B model consumes more than 20G memory, which is larger than memory of one GPU.
-
Hello, @Snosixtyboo @ameuleman my device is 4090 24G.
First,when using the SIBR viewer to view my trained model (model size is 4G), I found that the gpu memory is about 22G, if this is the case, if…
-
**Severity**: Medium
**Vulnerability Details**:
Even after fixing the dynamic size allocation, there is a bug where retData is still pre-allocated to a fixed size (2 * 32 bytes). This allocation s…
-
Hello, Thanks for this library; I like your approach to the problem. But I was testing and it seems to be using more GPU memory than I expected?
If I simply change the `grid_num` in the `examples/t…
jtbr updated
5 months ago