| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Community
Forum: Hardware Chat Room
Thread: Windows 10 |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 104
|
|
| Author |
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Found the hallelujah article to the Windows 10 network port bridging problem at http://www.windowscentral.com/how-set-and-man...dge-connection-windows-10
----------------------------------------Now read carefully, for that is not made clear in the article: BEFORE you create the bridge between the 2 network ports Wifi To Ethernet, enter the fixed IPv4/DNS information ** into the Wifi Adapter as AFTER the bridging, the IPv4 Properties / configuration section is no longer accessible (and only Dataman's Soup Nazi knows why). This is different also from W7: When done, your Wifi host appears on your router's connected devices table, and the hosted device, the one that internet/LAN connects through the host, will NOT show up... it does not seem to exist to the router as the bridge host acts as a secondary LAN router (The ethernet card shows an entirely different set of Device/Gateway IPs. To make matter more confusing, the HOST shows in the router device table with the host name, but with the IP of the hosted device (that was hard entered too). Anyway, in this department clam happy again, and not going to fix anything as now it is not broken (Till MS does something to the broth again).  ** I use OpenDNS as primary DNS server and Google as secondary, much better than the ones of the ISP. [Edit 1 times, last edit by SekeRob* at Aug 28, 2016 4:19:19 PM] |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Back on Swap File aka Virtual Memory, found a newer document by the hand of MS themselves, who now are advising on setting minimum to 1xRAM size and Max as 4x RAM, yes 4x. That's major if the same CPU would have 4GB RAM at disposal opposed to 8GB, which mine has. We tried and low and behold, still sticking to the signed out, all accounts regimen, now observe 99.94% efficiency on 8 UGM jobs in various states of progress. Set Write to Disk to 300 seconds yesterday and did boot after changing the swap settings, so there is something too the 'humongous' VM specifying.
Opposed, my multiboot system descended to just 70% efficiency on Zika with same sign-out strategy... signing in speeds things up, so what on earth in going on behind me back :? For sure, just received another mega build update (Slow Ring 14393.103) lasting several hours to boot and boot again, before the same VM approach will get it's chance to do a show-off. Will know tomorrow if there a change for the better. |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Well, Well, Well, Q6600 4 core computer, circa 2005, only able to use 3GB RAM, though it has 4 (BIOS un-updatable), and this one set to minimum VM of 3076MB and max of 12304, booted ones more and observed with BOINCTasks from remote...
-Initially 4 Zika crunched at about 85% (much better than 70) -Then it started to drop rapidly to 70ish, but then -Things started to climb and by the time 1st was finished in 1:37 hours, it ended with 92.7% -Then the next and the next started whilst and these babies rapidly climbed to 99.8%, where they stayed. Got an HST too, and that one went and stayed on 99.8% too, with a WtD of 600 seconds. Soooo, what seems to be the case is, wild guessing, Windows 10 starts up piles of svchost dlhost and more processes, each wanting a 2GB VM allocation (my 8 core desktop has 63 of these ATM), to include Runtimebroker, which has massive Page Faulting on top, though the delta indicates none to few. Once things have settled, most of that dung is considered not to be needed in RAM and is quasi permanent relegated to VM, minimal swapping needed if at all, which is the point where the near perfect BOINC efficiency starts counting of 99.8+, even on old hardware. Is there some 'virtualization' going on in W10 v.v. 2GB blocks? (no hits at all on Google to disclose the reason  )Still, amazement, and for anything less than 99.8 it's not good enough  BTW, the PhD label designated is French for Professeure d'haute Drivèlle (if you follow my drift)  |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Maybe this Q&A has the VM allocation answer... Superfetch and 'in memory' compression, but it is by design so is suggested (has to be as it's seen on 3 different systems here).
http://superuser.com/questions/952141/windows...ng-massive-amounts-of-ram , as of build 10525 i.e. the original W10 of august 2015 did not have this! In Windows 10, we have added a new concept in the Memory Manager called a compression store, which is an in-memory collection of compressed pages. This means that when Memory Manager feels memory pressure, it will compress unused pages instead of writing them to disk. This reduces the amount of memory used per process, allowing Windows 10 to maintain more applications in physical memory at a time. This also helps provide better responsiveness across Windows 10. The compression store lives in the System process’s working set. Since the system process holds the store in memory, its working set grows larger exactly when memory is being made available for other processes. This is visible in Task Manager and the reason the System process appears to be consuming more memory than previous releases. So instead of writing memory data to the pagefile it compresses them. And this compressed memory is shown in the System process.Microsoft also posted more details in the inside hub. Winbeta created a article which includes more details. Apparently, the reason for this happened to do with Microsoft choosing to suspend UWP apps when they were not in the foreground, very similar to some smartphone OS management. Windows 8 users understood (perhaps not) that if apps weren’t on screen, they wouldn’t run until the user switched back to them. The ‘all or nothing’ approach is being updated with Windows 10 introducing a layer between the pagefile and normal paging activity. Now, when faced with memory pressure issues, MM will determine which pages should be moved to the modified list in a process called trimming. The modified list is a secondary list of pagefiles backing up a list of standby pagefiles. A backup list is captured in case memory is reclaimed from the standby list by another process, and the original process comes looking for its page. Instead of all or nothing, Windows 10 MM will compress unused pages rather than writing them to disk. With less writing, the result should be fewer disk operations – thanks to the compression – and now more data can be stored in memory. |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Back on Swap File aka Virtual Memory, found a newer document by the hand of MS themselves, who now are advising on setting minimum to 1xRAM size and Max as 4x RAM, yes 4x. That's major if the same CPU would have 4GB RAM at disposal opposed to 8GB, which mine has... So MS is recommending that my W10 computer with 32GB RAM needs a 128GB pagefile?! I think when I set up the system I told it max 4GB pagefile an directed it to my secondary platter drive. If I used MS recommendations, my 250GB SSD would be completely full, between OS and pagefile allocations  |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Would take it at Trial & Error face value... it was 'newer' advice but from the build 10240 days (which is when my multi-boot had good efficiency, which went south with 14393). If your 32GB Ram device does well, don't 'fix'.
Watched a video by one of the designers, the interesting part being that the in-memory compressed pages eventually do get written to the VM, as-is, which is 60-70 percent smaller in size than in past, modern systems supposedly reaching decompression rates of 7GB per second (a surface-pro still reaching 600MB/sec)... kind of unnoticeable by the user. With the 4770K being last to get the treatment, 8GB Ram, the initial boot took longer, possibly because it was setting up the big VM space, but now things are flying. There's supposedly a 'Memory Compression' process now broken out Back to study the new school books  |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
For today's installment of Windows 10 'Insider', the latest can break your WiFi thoroughly and completely, as MS now also acknowledges, with the only fix there being is to roll out the Ethernet cable to your modem/router (which unless you have a Gigabit version relegates you to 100MB LAN speed), or roll-back using recovery.
Edge is still not starting up, after another run at MS instructions to clean all related out and reapply 'Edge' defaults. Who said it aint half bad ;? More on the pagefile (VM) topic, downloaded AusLogic Free v7 (last I had was a v6 of 2012), and scheduled it to do a boottime defrag of the pagefile and various other files such as MFT and hiberfil which are locked whilst Windows is running. Took 10 minutes and now they are in one contiguous place, instead of the many, so the defrag analysis report said. |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Pulled at Reddit, and supposedly from the XP days and before ... I did not know, but if you open up your volume control applet and have a mouse wheel, just roll it up or down.
 |
||
|
|
nanoprobe
Master Cruncher Classified Joined: Aug 29, 2008 Post Count: 2998 Status: Offline Project Badges: 
|
----------------------------------------
In 1969 I took an oath to defend and protect the U S Constitution against all enemies, both foreign and Domestic. There was no expiration date.
  |
||
|
|
SekeRob
Master Cruncher Joined: Jan 7, 2013 Post Count: 2741 Status: Offline |
Here is the solution for resetting Edge if it keeps crashing right from the blue launch screen (it's needed to get Cortana to fetch anything on the intertubes, sadly, no way to make it use another mature browser). Visit http://n4bb.com/how-to-reset-microsoft-edge-on-windows-10/ and try the Last solution, clearing out the MS.Edge folder in Appdata, then run a PowerShell command as admin.
(Amazingly, once I stumbled on this, knew where what to look for, found it also on the MS Support forums, going back to mid 2015, yes this bug continues unresolved since W10 launch.) |
||
|
|
|