Memory issues...
-
I hope you realize that Edge now uses the same core chromium engine as Chrome?
You realize one is "wrapped" by Google and the other by MS?
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
You realize one is "wrapped" by Google and the other by MS?
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
Of course. And is one really all that much better than the other?
-
My coworker has a brand new 16GB laptop. 16GB should be enough for most workloads, or so you'd think. Unfortunately, that is not the case. We're running "the usual", such as Outlook, Spotify, SourceTree, Teams, Chrome, OneDrive, etc. Now, with only two Visual Studio instances and a SQL Server Management Studio instance open, SQL Server (the service) just chokes. We're getting timeouts like you wouldn't believe, nothing works. After some digging, we found the reason to be memory exhaustion, 16GB just went up in smoke and it's at its peak at a constant 90+%. I've had 16GB and even less in the past, and running a local SQL Server instance together with VS and SSMS has never been a problem. At this point it's become unworkable. You'd think that maybe the memory would be more evenly distributed and that some processes would write to disk instead and become a bit slower. But instead, SQL Server just pretty much stops working altogether. Closing a VS instance fixes the problem, but sometimes we just need to have two instances open. My coworker changed his virtual memory page file to use 20GB and that fixes the problem, but doesn't feel right. Anyone have any ideas what the problem could be?* * Is this a programming question? Is it a SQL Server question? Is it a general computing question? I'm not sure, so I'm posting it here.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
Sorry, I run VMs all the time on my main development laptop... that might end shortly due to retirement and other personal issues, but the last 3 laptops I've had - unit -1 (sitting on the shelf), unit 0 (I'm typing on it) and unit 1 (the new one that I am migrating too) all have 64GB. It's a defense against the Microsoft virus. Oh, the Xp VM runs all day long with 2GB, Win 10 loves 16GB, Win 11 meh, not there yet. Tried to get a 16gb machine up with a VM and it choked.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
I decided to take the elephant by the tusks, so to speak, and ordered a new Dell XPS laptop fully loaded - I9 processor, 64G RAM, 1TB SSD drive and a quad density touch screen. Was pricey, but this will last me for the next 5+ years without mucking about with upgrades. Did the same with my previous laptop, and it served me well fo 10+ years. Not screwing around anymore... And this thing is awesomely fast. It can do a VS update 3x faster than my work computer. I have no complaints...
Andreas Mertens wrote:
it served me well fo 10+ years. Not screwing around anymore...
I purchased my DELL work laptop when leaving the 2.previous company (10€ symbolic price to avoid "present" due to legislation) and it is still performing good, only mucking is temperature and changing the radiator is a PITA (I saw it back then done by the technician and I won't start with it). I might give the CPU a bit of thermal paste, but if not... not a big issue, Laptop was bought in 2011 and still kicking. I bought an ACER out of the box in an offer as Multimedia device for the living room in 2017... still working really good. I think I won't ever pimp any laptop beyond changing the disk or adding RAM. But I built my PC myself from the scratch, I had no hurry, so I just purchased the parts during a couple of months while waiting for good offers, the only really costy thing was the graphic card. It was during the time they were way overpriced and I bought it for the official price (what already was a really good price back then, all other shops were at least 50% more expensive). This I didn't do only because of price (which still got me around 1k savings comparing with current shop prices at the moment) but mostly, I did it to get back up-to-date in Hardware. My last built was over 10-11 years before that. I expect this PC to be good for the next 10 years or so (again). For the kids I will not build the pc, just buy a pre-build setting. Only re-install to get the system as clean as I can (and the current windows version of the moment allows me)
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
Sorry, I run VMs all the time on my main development laptop... that might end shortly due to retirement and other personal issues, but the last 3 laptops I've had - unit -1 (sitting on the shelf), unit 0 (I'm typing on it) and unit 1 (the new one that I am migrating too) all have 64GB. It's a defense against the Microsoft virus. Oh, the Xp VM runs all day long with 2GB, Win 10 loves 16GB, Win 11 meh, not there yet. Tried to get a 16gb machine up with a VM and it choked.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
Interesting you should compare Win 11 with the other OSs, we only started having issues with our massive 64GB memory all being gobbled up after we installed Win 11. There does seem to be something with Win 11 that is not quite right with VMs or WSL, as though there is a memory leak somewhere.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
Andreas Mertens wrote:
it served me well fo 10+ years. Not screwing around anymore...
I purchased my DELL work laptop when leaving the 2.previous company (10€ symbolic price to avoid "present" due to legislation) and it is still performing good, only mucking is temperature and changing the radiator is a PITA (I saw it back then done by the technician and I won't start with it). I might give the CPU a bit of thermal paste, but if not... not a big issue, Laptop was bought in 2011 and still kicking. I bought an ACER out of the box in an offer as Multimedia device for the living room in 2017... still working really good. I think I won't ever pimp any laptop beyond changing the disk or adding RAM. But I built my PC myself from the scratch, I had no hurry, so I just purchased the parts during a couple of months while waiting for good offers, the only really costy thing was the graphic card. It was during the time they were way overpriced and I bought it for the official price (what already was a really good price back then, all other shops were at least 50% more expensive). This I didn't do only because of price (which still got me around 1k savings comparing with current shop prices at the moment) but mostly, I did it to get back up-to-date in Hardware. My last built was over 10-11 years before that. I expect this PC to be good for the next 10 years or so (again). For the kids I will not build the pc, just buy a pre-build setting. Only re-install to get the system as clean as I can (and the current windows version of the moment allows me)
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
In my experience, the main cause of laptops running too hot is dust buildup in the air path through the radiator/heat exchanger/whatever-you-want-to-call-it, typically where the fan "pushes" the air. Most laptops are fairly easy to open up to the point that you can clean it out, and you can usually get instructions online. A couple of hp lappies I could open up to that point in about 5 minutes, maybe a dozen screws and a few clips. The worst was a 2006-or-so lenovo thinkpad, 30+ screws... But it's still running. Right now a friend is using it in the next room to scan about 1000 handwritten pages to PDF.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
-
Have you tried limiting how much memory SQL Server is allowed to use? It will take every bit of free memory on the machine as it needs it and tends to hold on to it long after that need is gone.
There are no solutions, only trade-offs.
- Thomas SowellA day can really slip by when you're deliberately avoiding what you're supposed to do.
- Calvin (Bill Watterson, Calvin & Hobbes)Yeah, but that wasn't the problem. The problem was SQL Server could not get enough memory to run properly, so we gave it a minimum amount of memory (and also a maximum). Works like a charm now :)
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
My coworker has a brand new 16GB laptop. 16GB should be enough for most workloads, or so you'd think. Unfortunately, that is not the case. We're running "the usual", such as Outlook, Spotify, SourceTree, Teams, Chrome, OneDrive, etc. Now, with only two Visual Studio instances and a SQL Server Management Studio instance open, SQL Server (the service) just chokes. We're getting timeouts like you wouldn't believe, nothing works. After some digging, we found the reason to be memory exhaustion, 16GB just went up in smoke and it's at its peak at a constant 90+%. I've had 16GB and even less in the past, and running a local SQL Server instance together with VS and SSMS has never been a problem. At this point it's become unworkable. You'd think that maybe the memory would be more evenly distributed and that some processes would write to disk instead and become a bit slower. But instead, SQL Server just pretty much stops working altogether. Closing a VS instance fixes the problem, but sometimes we just need to have two instances open. My coworker changed his virtual memory page file to use 20GB and that fixes the problem, but doesn't feel right. Anyone have any ideas what the problem could be?* * Is this a programming question? Is it a SQL Server question? Is it a general computing question? I'm not sure, so I'm posting it here.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
Visual studio 2022 I presume. Make it run at 32 bits, that will save your memory. (or use 2019) Unless of course your programs are humungous. :-)
Wrong is evil and must be defeated. - Jeff Ello
-
In my experience, the main cause of laptops running too hot is dust buildup in the air path through the radiator/heat exchanger/whatever-you-want-to-call-it, typically where the fan "pushes" the air. Most laptops are fairly easy to open up to the point that you can clean it out, and you can usually get instructions online. A couple of hp lappies I could open up to that point in about 5 minutes, maybe a dozen screws and a few clips. The worst was a 2006-or-so lenovo thinkpad, 30+ screws... But it's still running. Right now a friend is using it in the next room to scan about 1000 handwritten pages to PDF.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
Yeah I know, I do it more or less periodically, but back then (2 years in my "possesion" a lot of projects on the field and a couple of accidental hits), the technician changed the mechanical part. Sadly to do that it was needed to take a good part of the laptop off, including monitor due to not so clever distribution (next model is way easier to do it). I think that could be again the same problem (aprox 10 years later) because cleaning up the airflow way (the comfortable part) makes no substantial difference, maybe makes it a couple of degrees less hot, but it definitivelly is not cool as it should
M.D.V. ;) If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about? Help me to understand what I'm saying, and I'll explain it better to you Rating helpful answers is nice, but saying thanks can be even nicer.
-
My coworker has a brand new 16GB laptop. 16GB should be enough for most workloads, or so you'd think. Unfortunately, that is not the case. We're running "the usual", such as Outlook, Spotify, SourceTree, Teams, Chrome, OneDrive, etc. Now, with only two Visual Studio instances and a SQL Server Management Studio instance open, SQL Server (the service) just chokes. We're getting timeouts like you wouldn't believe, nothing works. After some digging, we found the reason to be memory exhaustion, 16GB just went up in smoke and it's at its peak at a constant 90+%. I've had 16GB and even less in the past, and running a local SQL Server instance together with VS and SSMS has never been a problem. At this point it's become unworkable. You'd think that maybe the memory would be more evenly distributed and that some processes would write to disk instead and become a bit slower. But instead, SQL Server just pretty much stops working altogether. Closing a VS instance fixes the problem, but sometimes we just need to have two instances open. My coworker changed his virtual memory page file to use 20GB and that fixes the problem, but doesn't feel right. Anyone have any ideas what the problem could be?* * Is this a programming question? Is it a SQL Server question? Is it a general computing question? I'm not sure, so I'm posting it here.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
SQL Server loves memory. If you're running an SQL Server instance on the same machine, throttle the amount of memory that SQL uses from the default value of "as much as I can get" down to something resonable.
-
My coworker has a brand new 16GB laptop. 16GB should be enough for most workloads, or so you'd think. Unfortunately, that is not the case. We're running "the usual", such as Outlook, Spotify, SourceTree, Teams, Chrome, OneDrive, etc. Now, with only two Visual Studio instances and a SQL Server Management Studio instance open, SQL Server (the service) just chokes. We're getting timeouts like you wouldn't believe, nothing works. After some digging, we found the reason to be memory exhaustion, 16GB just went up in smoke and it's at its peak at a constant 90+%. I've had 16GB and even less in the past, and running a local SQL Server instance together with VS and SSMS has never been a problem. At this point it's become unworkable. You'd think that maybe the memory would be more evenly distributed and that some processes would write to disk instead and become a bit slower. But instead, SQL Server just pretty much stops working altogether. Closing a VS instance fixes the problem, but sometimes we just need to have two instances open. My coworker changed his virtual memory page file to use 20GB and that fixes the problem, but doesn't feel right. Anyone have any ideas what the problem could be?* * Is this a programming question? Is it a SQL Server question? Is it a general computing question? I'm not sure, so I'm posting it here.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
Make sure you limit the amount of memory that the SQL Server service uses. By default, it will grow to use all memory available!
-
My coworker has a brand new 16GB laptop. 16GB should be enough for most workloads, or so you'd think. Unfortunately, that is not the case. We're running "the usual", such as Outlook, Spotify, SourceTree, Teams, Chrome, OneDrive, etc. Now, with only two Visual Studio instances and a SQL Server Management Studio instance open, SQL Server (the service) just chokes. We're getting timeouts like you wouldn't believe, nothing works. After some digging, we found the reason to be memory exhaustion, 16GB just went up in smoke and it's at its peak at a constant 90+%. I've had 16GB and even less in the past, and running a local SQL Server instance together with VS and SSMS has never been a problem. At this point it's become unworkable. You'd think that maybe the memory would be more evenly distributed and that some processes would write to disk instead and become a bit slower. But instead, SQL Server just pretty much stops working altogether. Closing a VS instance fixes the problem, but sometimes we just need to have two instances open. My coworker changed his virtual memory page file to use 20GB and that fixes the problem, but doesn't feel right. Anyone have any ideas what the problem could be?* * Is this a programming question? Is it a SQL Server question? Is it a general computing question? I'm not sure, so I'm posting it here.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
As always, the answer is: it depends. :) You don’t say what version SQL server is running, or what the load is. But, you will probably want to set the service’s MIN and MAX memory allocation. Unfettered, the service will take as much memory as it can, and not release it unless caches are cleared. Hopefully it’s only being used as a development server and has only your coworker’s load on it. We always put our SQL servers (dev,staging, and production) on separate network machines. Good luck.
Time is the differentiation of eternity devised by man to measure the passage of human events. - Manly P. Hall Mark Just another cog in the wheel
-
I decided to take the elephant by the tusks, so to speak, and ordered a new Dell XPS laptop fully loaded - I9 processor, 64G RAM, 1TB SSD drive and a quad density touch screen. Was pricey, but this will last me for the next 5+ years without mucking about with upgrades. Did the same with my previous laptop, and it served me well fo 10+ years. Not screwing around anymore... And this thing is awesomely fast. It can do a VS update 3x faster than my work computer. I have no complaints...
Andreas Mertens wrote:
Not screwing around anymore...
Exactly, my man. We just reach a point in life where tinkering around isn't feasible anymore. Priorities and all that.
Jeremy Falcon
-
jschell wrote:
But you didn't mention the CPU at all? When this happens the CPU is low? Also which version of windows?
CPU isn't the issue, the guy has a good one. Windows 11 Pro.
jschell wrote:
And what was it set to before? Mine uses auto manage.
Same.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
My coworker has a brand new 16GB laptop. 16GB should be enough for most workloads, or so you'd think. Unfortunately, that is not the case. We're running "the usual", such as Outlook, Spotify, SourceTree, Teams, Chrome, OneDrive, etc. Now, with only two Visual Studio instances and a SQL Server Management Studio instance open, SQL Server (the service) just chokes. We're getting timeouts like you wouldn't believe, nothing works. After some digging, we found the reason to be memory exhaustion, 16GB just went up in smoke and it's at its peak at a constant 90+%. I've had 16GB and even less in the past, and running a local SQL Server instance together with VS and SSMS has never been a problem. At this point it's become unworkable. You'd think that maybe the memory would be more evenly distributed and that some processes would write to disk instead and become a bit slower. But instead, SQL Server just pretty much stops working altogether. Closing a VS instance fixes the problem, but sometimes we just need to have two instances open. My coworker changed his virtual memory page file to use 20GB and that fixes the problem, but doesn't feel right. Anyone have any ideas what the problem could be?* * Is this a programming question? Is it a SQL Server question? Is it a general computing question? I'm not sure, so I'm posting it here.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
Sort of a side issue, but pay attention to what you buy. I'm on my third Eluktronics laptop - sort of a custom small shop, and I love the fact that they _never_ install bloatware. That said, I picked up a laptop for my wife with the assumption that I could add ram if she needed it. The spec was very subtle, and I missed the fact that the 16GB ram was soldered to the motherboard. No extra memory slots as well. I never even thought to look. This seems to happen if you get a very slim design. My new laptop (same maker) does not have this issue. What I find interesting in this discussion is the fact that Windows just does not seem to manage memory as one might expect. It's like the memory manager is brain dead.
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
Of course. And is one really all that much better than the other?
Not "better" ... greedier at collecting data and calling home. I said Chrome was always "busy"; including tasks like "GoogleUpdate"; or whatever.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
-
My coworker has a brand new 16GB laptop. 16GB should be enough for most workloads, or so you'd think. Unfortunately, that is not the case. We're running "the usual", such as Outlook, Spotify, SourceTree, Teams, Chrome, OneDrive, etc. Now, with only two Visual Studio instances and a SQL Server Management Studio instance open, SQL Server (the service) just chokes. We're getting timeouts like you wouldn't believe, nothing works. After some digging, we found the reason to be memory exhaustion, 16GB just went up in smoke and it's at its peak at a constant 90+%. I've had 16GB and even less in the past, and running a local SQL Server instance together with VS and SSMS has never been a problem. At this point it's become unworkable. You'd think that maybe the memory would be more evenly distributed and that some processes would write to disk instead and become a bit slower. But instead, SQL Server just pretty much stops working altogether. Closing a VS instance fixes the problem, but sometimes we just need to have two instances open. My coworker changed his virtual memory page file to use 20GB and that fixes the problem, but doesn't feel right. Anyone have any ideas what the problem could be?* * Is this a programming question? Is it a SQL Server question? Is it a general computing question? I'm not sure, so I'm posting it here.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
-
My coworker has a brand new 16GB laptop. 16GB should be enough for most workloads, or so you'd think. Unfortunately, that is not the case. We're running "the usual", such as Outlook, Spotify, SourceTree, Teams, Chrome, OneDrive, etc. Now, with only two Visual Studio instances and a SQL Server Management Studio instance open, SQL Server (the service) just chokes. We're getting timeouts like you wouldn't believe, nothing works. After some digging, we found the reason to be memory exhaustion, 16GB just went up in smoke and it's at its peak at a constant 90+%. I've had 16GB and even less in the past, and running a local SQL Server instance together with VS and SSMS has never been a problem. At this point it's become unworkable. You'd think that maybe the memory would be more evenly distributed and that some processes would write to disk instead and become a bit slower. But instead, SQL Server just pretty much stops working altogether. Closing a VS instance fixes the problem, but sometimes we just need to have two instances open. My coworker changed his virtual memory page file to use 20GB and that fixes the problem, but doesn't feel right. Anyone have any ideas what the problem could be?* * Is this a programming question? Is it a SQL Server question? Is it a general computing question? I'm not sure, so I'm posting it here.
Best, Sander Azure DevOps Succinctly (free eBook) Azure Serverless Succinctly (free eBook) Migrating Apps to the Cloud with Azure arrgh.js - Bringing LINQ to JavaScript
In SSMS (SQL Server Management Studio), right click on the server instance and select properties. There it will tell you how much memory it's using and have some settings for limiting it.
Bond Keep all things as simple as possible, but no simpler. -said someone, somewhere
-
I'm not sure anyone ever needs to admit that. :) It's a physical constant. Do you have any idea how memory expensive new icons are? Re-arranging menus just to re-arrange them? lol
Charlie Gilley “They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759 Has never been more appropriate.
-
SQL Server loves memory. If you're running an SQL Server instance on the same machine, throttle the amount of memory that SQL uses from the default value of "as much as I can get" down to something resonable.
I guess that if it by default limited itself to, say, 2 GB, there would be a number of people standing up and shouting: "Silly database system, not making use of the resources available to it!" Especially when we are talking about a server: Server software is primarily architected to run on a more or less dedicated server machine. Then it makes perfectly sense to default to using all memory (and other) resources available. As long as there is a way in a non-dedicated-machine environment to reduce the resource consumption, that is fine with me. Side note: I am not familiar with the MS SQL Server. But, I have several times had to explain to (non-professional) hacker friends that when the Resource Monitor shows less than 10% "Free" memory, it does not imply that they should double their RAM, when 75% of the memory is marked as "Standby". "Standby" memory is like "Take it if you need it, but as long as you don't ask for it, I keep track of which data was left behind when it was abandoned, just in case someone comes along wanting exactly that piece of data." If some database system (SQL server or any other) handles memory in a similar way, saying "As long as noone else need this memory, I will use it as a disk cache area, but I am willing to give it up on short notice when someone asks", then that should be perfectly OK, even if it looks as if it is hogging all RAM. Please note: I do not know if this is the case for SQL server or any other given DBMS. It could be implemented that way. A DBMS never has any significant backlog of modified pages; after a commit, all changed data have been written to stable storage. So giving up a gigabyte of RAM does not require writing back a gigabyte to disk.
