Someone gone insane...
-
Kornfeld Eliyahu Peter wrote:
less than 20 solutions
Depends how big and/or complicated those projects are. Did you expand the node in Task Manager to check which sub-process was using the memory? What happens if you try building the solution with
dotnet buildfrom the command-line?
"These people looked deep within my soul and assigned me a number based on the order in which I joined." - Homer
Richard Deeming wrote:
Depends how big and/or complicated those projects are.
Nothing special about those project - most of them a few lines only...
Richard Deeming wrote:
What happens if you try building the solution with dotnet build from the command-line?
It is much faster and do not hit event the 1GB boundary...
"Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid." ― Albert Einstein
-
Can you think any justification to VS 2022 to hold to over 8GB of memory while compiling a solution with less than 20 solutions in it?
"Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid." ― Albert Einstein
If it has windows forms or components in it - anything with a designer, it will be loading your built binaries into your process so that it can update the visual designer aspects. And since they are (I am assuming here) .NET, that requires the CLI which tends to preallocate gobs of RAM for doing just about anything. If I had to guess, I'd say that's at least in part what it is, based on what you wrote.
To err is human. Fortune favors the monsters.
-
If it has windows forms or components in it - anything with a designer, it will be loading your built binaries into your process so that it can update the visual designer aspects. And since they are (I am assuming here) .NET, that requires the CLI which tends to preallocate gobs of RAM for doing just about anything. If I had to guess, I'd say that's at least in part what it is, based on what you wrote.
To err is human. Fortune favors the monsters.
It is a .NET Core (Blazor) app... And the code and the final binary is less then a 100 Mb combined... And if I do the compilation from the command line it is much faster and eats almost 90% less memory...
"Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid." ― Albert Einstein
-
It is a .NET Core (Blazor) app... And the code and the final binary is less then a 100 Mb combined... And if I do the compilation from the command line it is much faster and eats almost 90% less memory...
"Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid." ― Albert Einstein
Then it's almost certainly loading those binaries, like I said. Assuming Blazor has designers. The command line isn't going to load the designers, so no need to load the binaries it just compiled into the process address space.
To err is human. Fortune favors the monsters.
-
Can you think any justification to VS 2022 to hold to over 8GB of memory while compiling a solution with less than 20 solutions in it?
"Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid." ― Albert Einstein
Kornfeld Eliyahu Peter wrote:
a solution with less than 20 solutions in it?
20 solutions, or 20 projects? I understand that solutions can include solutions of their own, but I've never had to do that. And since each solution, by itself, can contain any number of projects...I'm not entirely surprised. I have a solution with ~20 projects (not solutions), and that can take up ~2GB of RAM...but, that's with R#, which is demonstrably still a pig.
-
To seem important? I know some developers increase the size of their executables so customers don't have a reaction like "is that all" :-\
:-D
--- With regards... The nk.
-
Can you think any justification to VS 2022 to hold to over 8GB of memory while compiling a solution with less than 20 solutions in it?
"Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid." ― Albert Einstein
It's like driving a car with 4 extra seats and a top speed of >85mph to the shops across the street. And then, when you take it in for a simple repair, no-one has the replacement part in stock. Name's Logic, Applied Logic (Miss) ;)
-
Can you think any justification to VS 2022 to hold to over 8GB of memory while compiling a solution with less than 20 solutions in it?
"Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid." ― Albert Einstein
-
Kornfeld Eliyahu Peter wrote:
a solution with less than 20 solutions in it?
20 solutions, or 20 projects? I understand that solutions can include solutions of their own, but I've never had to do that. And since each solution, by itself, can contain any number of projects...I'm not entirely surprised. I have a solution with ~20 projects (not solutions), and that can take up ~2GB of RAM...but, that's with R#, which is demonstrably still a pig.
19 Projects in 1 Solution...
"Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid." ― Albert Einstein
-
Then it's almost certainly loading those binaries, like I said. Assuming Blazor has designers. The command line isn't going to load the designers, so no need to load the binaries it just compiled into the process address space.
To err is human. Fortune favors the monsters.
If the command line does not loads the designers (I didn't saw any designers for Blazor until now) they not needed for the compilation... Also - 8Gb of designers?!?!
"Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid." ― Albert Einstein
-
8 in theory, but because of the dependencies it is down to 5... But no difference there between VS and the command line...
"Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid." ― Albert Einstein
-
If the command line does not loads the designers (I didn't saw any designers for Blazor until now) they not needed for the compilation... Also - 8Gb of designers?!?!
"Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid." ― Albert Einstein
Yes. I explained all that in the first post. I'm not looking to do so again. Edit: Sorry when I wrote that I was tired. I'll explain this better. Visual Studio has designers. Designers work by accessing the code you JUST compiled. In order to do so, that code must be loaded into memory after it is compiled. Furthermore, .NET is very aggressive in terms of memory allocation, often allocating gigs ahead of time, so when you load these binaries you are tickling .NET's memory allocator again, and it's preallocating.
To err is human. Fortune favors the monsters.
-
Can you think any justification to VS 2022 to hold to over 8GB of memory while compiling a solution with less than 20 solutions in it?
"Everybody is a genius. But if you judge a fish by its ability to climb a tree, it will live its whole life believing that it is stupid." ― Albert Einstein
