mradermacher
commited on
Update README.md
Browse files
README.md
CHANGED
@@ -13,10 +13,16 @@ language:
|
|
13 |
|
14 |
## What does the "-i1" mean in "-i1-GGUF"?
|
15 |
|
|
|
|
|
16 |
## Why are you doing this?
|
17 |
|
|
|
|
|
18 |
## You have amazing hardware!?!?!
|
19 |
|
|
|
|
|
20 |
## Why don't you use gguf-split?
|
21 |
|
22 |
TL;DR: I don't have the hardware/resources for that.
|
@@ -31,3 +37,5 @@ requires special tools to manage, instead of supporting the tens of thousands of
|
|
31 |
could just be mmapped together into memory from split files. That doesn't keep me from supporting it, but it would have
|
32 |
been nice to look at the existing reality and/or consult the community before throwing yet another hard to support format out
|
33 |
there without thinking.
|
|
|
|
|
|
13 |
|
14 |
## What does the "-i1" mean in "-i1-GGUF"?
|
15 |
|
16 |
+
tbd
|
17 |
+
|
18 |
## Why are you doing this?
|
19 |
|
20 |
+
tbd
|
21 |
+
|
22 |
## You have amazing hardware!?!?!
|
23 |
|
24 |
+
tbd
|
25 |
+
|
26 |
## Why don't you use gguf-split?
|
27 |
|
28 |
TL;DR: I don't have the hardware/resources for that.
|
|
|
37 |
could just be mmapped together into memory from split files. That doesn't keep me from supporting it, but it would have
|
38 |
been nice to look at the existing reality and/or consult the community before throwing yet another hard to support format out
|
39 |
there without thinking.
|
40 |
+
|
41 |
+
There are some developments to make this less of a pain, and I will revisit this issue from time to time to see if it has become feasible.
|