Dann Corbit wrote: ↑Sat Aug 29, 2020 6:24 am
I think the embedded file is misguided.
For instance, I build a bunch of different binaries, and shall each one have a 20MB pile of goo sitting in it's data space?
Imagine if all of the stockfish variants follow suit.
Then we will have 3-4x 20MB pile multiplied by variant count.
I think it would make me cry,.
There is a reason we don't embed 5 man tablebase file sets in the binaries.
If it were that hard to browse to a file, nobody could use a tablebase.
Please, for the love of all that is good and true, no more embedding of 20MB files.
I move files across the network like mad. The volume of the file makes the virus scan time go up something like quadratically. A 20 MB file causes a big delay. A 60 MB file causes an atrocious delay. I do a build for each new variant of each new engine. We are talking about serious problems here.
Please, please, please. I am begging down on my knees. No embedding of TB files or Networks.
Dann Corbit wrote: ↑Sat Aug 29, 2020 6:24 am
I think the embedded file is misguided.
For instance, I build a bunch of different binaries, and shall each one have a 20MB pile of goo sitting in it's data space?
Imagine if all of the stockfish variants follow suit.
Then we will have 3-4x 20MB pile multiplied by variant count.
I think it would make me cry,.
There is a reason we don't embed 5 man tablebase file sets in the binaries.
If it were that hard to browse to a file, nobody could use a tablebase.
Please, for the love of all that is good and true, no more embedding of 20MB files.
I move files across the network like mad. The volume of the file makes the virus scan time go up something like quadratically. A 20 MB file causes a big delay. A 60 MB file causes an atrocious delay. I do a build for each new variant of each new engine. We are talking about serious problems here.
Please, please, please. I am begging down on my knees. No embedding of TB files or Networks.
I hope that there are some simple instructions for removal.
Taking ideas is not a vice, it is a virtue. We have another word for this. It is called learning.
But sharing ideas is an even greater virtue. We have another word for this. It is called teaching.
Joerg Oster wrote: ↑Sat Aug 29, 2020 11:14 pm
I can't believe it ...
I think it is useful for official releases. There are probably many users that download Stockfish at most once a year and would have a lot of trouble to configure the network file correctly.
For developers and advanced users, embedded network files are just a nuisance.
Storing dozens of different Stockfish versions that share the same main net and have only minor differences between them or just some search changes is a niche use case.
The solution to an embedded net appears simple to me, for those against embedding. I can understand the confusion of a once a year download user where an embedded net would be easy to install, so in that situation I support and applaud the idea of an embedded net file. For those who understand how to point (set the path) to an external netfile why not have a checkbox in the param file labelled something like 'use embedded net'. Ticked = use embedded, unticked = use external net.
It is an exciting time to be able to play around with netfiles to determine how the program reacts with different files.
Naturally the 'annual download merchant' would be happy to have a working program without the netfile hassle and the experimenter can tweak to his hearts desire.
syzygy wrote: ↑Sun Aug 30, 2020 4:21 am
...
I think it is useful for official releases. There are probably many users that download Stockfish at most once a year and would have a lot of trouble to configure the network file correctly.
For developers and advanced users, embedded network files are just a nuisance.
I agree.
As we can see on abrok.eu/stockfish site nowadays the newer and newer Stoclfish have only small difference in code and in Elo. So if somebody use for e.g. 20200806 dated Stockfish with the most stronger NNUE-net
(nn-82215d0fd0df-814.bin) he get near the same Stockfish as he use the last "embedded" version.
Note
1, I do not like if a program is bounded to the Net, especially in the phase of compilation.
Net is a dangerous place for every program and I want to defense my machine and my own Stockfish from any danger on the Net.
2, Developer of Stockfish said they made a "simplified" Make - file for Stockfish, but they forgot to mention which Windows compiler is good for the new Stockfish and its "simple" Make- file.
For the "Classical" Stockfish is good the Mingw-gcc x86-64 compiler, but who know what is good for NON-EMBEDDED! SF+NNUE - version?
Dann Corbit wrote: ↑Sun Aug 30, 2020 12:43 am
I hope that there are some simple instructions for removal.
"It is possible to disable embedding, and instead specify a specific directory, e.g. linux distros might want to use
CXXFLAGS="-DNNUE_EMBEDDING_OFF -DDEFAULT_NNUE_DIRECTORY=/usr/share/games/stockfish/" make -j ARCH=x86-64 profile-build"
Indeed, the following command invoked from the Stockfish/src directory will download the default net (if not already present) to that directory and build a stockfish binary free from having an embedded net. By default, that binary will use the net that was just download, and will find it without issue.
Dann Corbit wrote: ↑Sat Aug 29, 2020 6:24 am
I think the embedded file is misguided.
For instance, I build a bunch of different binaries, and shall each one have a 20MB pile of goo sitting in it's data space?
Imagine if all of the stockfish variants follow suit.
Then we will have 3-4x 20MB pile multiplied by variant count.
I think it would make me cry,.
There is a reason we don't embed 5 man tablebase file sets in the binaries.
If it were that hard to browse to a file, nobody could use a tablebase.
Please, for the love of all that is good and true, no more embedding of 20MB files.
I move files across the network like mad. The volume of the file makes the virus scan time go up something like quadratically. A 20 MB file causes a big delay. A 60 MB file causes an atrocious delay. I do a build for each new variant of each new engine. We are talking about serious problems here.
Please, please, please. I am begging down on my knees. No embedding of TB files or Networks.
