Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


Search the Community

Showing results for tags 'Performance'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • The General Stuff
    • Announcements
    • Introduce Yourself!
    • General Discussion
  • Microsoft Software Products
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Server 2008/2012/2016
    • Older Windows NT-Family OSes
    • Windows 9x/ME
    • Other Microsoft Products
  • Unattended Windows Discussion & Support
    • Unattended Windows
    • Other Unattended Projects
  • Member Contributed Projects
    • Nuhi Utilities
    • Member Projects
    • Other Member Contributed Projects
    • Windows Updates Downloader
  • Software, Hardware, Media and Games
    • Forum Categories
    • Mobile Devices
  • Customizing Windows and Graphics
    • Customizing Windows
    • Customizing Graphics
  • Coding, Scripting and Servers
    • Web Development (HTML, Java, PHP, ASP, XML, etc.)
    • Programming (C++, Delphi, VB/VBS, CMD/batch, etc.)
    • Server - Side Help (IIS, Apache, etc.)
  • X's Concepts
  • The Compaq Computer Corporation Club's Discussion

Calendars

There are no results to display.

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype

Found 4 results

  1. Feel free to donate me something as a sign of appreciation for the UOC Patch and the Enforcer. Click on the "Donate" button to donate with PayPal: *UPDATE!* I have done some major reworks to the previous version, as I have found some bugs that for some reason I overlooked. I also have implemented some new entries in the UOC Enforcer, which seems to further improve performance, at least on my machine. The UOC Enforcer is now is required in order to fully enjoy the optimizations introduced by the new version. So, do not forget to install both the UOC Patch and the Enforcer! An explanation on how to install the UOC Enforcer is written below, right in this post. Build number is N2H. A brief introduction Hi everybody, I'm writing this thread because I would like to share with you an experiment I made as a result of two years of using an old, single core system (an overclocked Pentium III-S Tualatin 1.4GHz) with the modern web. As you all know, the most versatile and useful web browser to use for old machines, especially XP ones, is Mozilla Firefox, thanks to its customizability, the numerous forks that it spawned and the built in certificates manager that makes things easier if we want to connect old computers to the internet. This thread focuses specifically on @roytam1's browsers for XP, such as New Moon 27 SSE and Firefox 45 ESR SSE, because they are the ones I use on my Pentium III system and the ones I used as a base to develop my "patch". We know that old computers, especially if single core or SSE only systems, can struggle a bit with the stock versions of these browsers, because they are quite resource intensive, and so the experience is quite limited unless you have an hardware that is capable enough to run the browser comfortably. So, a year ago, back when my Tualatin was still a 800Mhz Coppermine system, I started delving into the about:config of Pale Moon first, and New Moon later, in order to reduce as much CPU and RAM consumption as possible. Had to do several trials and errors, but in the end, I finally managed to get improvements in responsiveness and overall speed on the browser and so, after six revisions, I officially want to release the UOC Patch, my personal attempt, inspired by the community and by my experience of using an old computer as a daily driver, at making web browsing with Firefox and derivatives a much more enjoyable experience. Ok ok, good. So what's the UOC Patch? The UOC Patch (shortened form of Ultra One Core Patch) is a custom Global Preferences file available for any Mozilla based browser that uses the codebase of Firefox 38 ESR (such as Pale Moon and Roytam1's New Moon) or Firefox 45 ESR (i.e. Firefox 45 ESR SSE always by Roytam1), that is aimed at optimizing the browser to run on old machines and to consume less resources. Bear in mind that I developed the UOC Patch for my machine, which used to be a 800Mhz Coppermine and now is an overclocked 1.4GHz Tualatin, so it might perform differently on yours, but it should bring some improvement in terms of speed. The UOC Patch is a Defaults Override file, meaning that it goes in the following directory "C:\Program Files\{Your Mozilla based browser}\Defaults\Pref\". As soon as you put the patch into the "Pref" folder, the default about:config parameters will be replaced by the ones of the patch, unless you have modified the same parameters. If so, you can switch to the UOC Patch parameters by simply resetting them in the about:config. The UOC Patch is not compatible with Firefox Quantum. The requirements? Surely it has them. Well, yeah. The UOC Patch requires at least a DirectX 9 capable graphics card. Even though it will work on a DirectX 8 card, I don't have one I can use to test it so it's pretty much untested. I tested the patch with a Geforce FX5500, an FX5600, a 6800GT and an ATI Radeon HD3850 and my current graphics card, an X1950 Pro, and the patch speeds up the browser as it should. Then, ideally, the CPU. A 800MHz CPU and higher can give you a better experience, again, I don't know how it does perform on a slower CPU. RAM wise, any system that can run New Moon 27 and derivatives or Firefox 45 ESR SSE will support the UOC Patch without issues. So, to recap, you need: A DirectX 9c capable graphics card with at least a 128 bit buss A 800MHz CPU or faster for better performance Enough RAM to support New Moon 27/Firefox 45 ESR SSE and other Roytam1's Mozilla based browsers Ok now that we know the specs, how to install it? Installing the UOC Patch is a very easy process. Just go in your browser folder (C:\Program Files\Mozilla Firefox or Pale Moon or any other Mozilla based browser you use), then go in the "Defaults" then the "Pref" folder and extract the UOC_Patch38.js or UOC_Patch45.js you will find in their respective archive in the above folder and start the browser. The UOC Patch will be automatically applied alongside your existing preferences. But as a safety measure, do make a backup of your prefs.js file inside your profile folder, before launching the patched browser. In order to access your profile folder, you must make sure that the hidden folders are visible (if not, you must go in the Control Panel, then choose Folder Options, and tick the box that says "Show Hidden Folders"), then navigate to your Firefox/New Moon/Mozilla browser profile folder (i.e. C:\Documents and Settings\{Your Username}\Application Data\Mozilla\Firefox\Profiles\{Your Profile Folder}), you will find a file called "prefs.js". Make a copy of the file and rename it to "prefs.bak" to back it up. For K-Meleon users, check out Mathwiz's post below: Enough with the words! I want to download it! Okay, okay. There you go. These are the download links for the UOC Patch. Remember, you must not absolutely use the UOC Patch for a particular codebase with a browser that uses a different one. You might experience issues. These two versions are conceived for the Firefox 38 ESR and 45 ESR codebases, so any fork of Firefox that uses those codebases, will work with their respective version of the patch. Choose carefully. For Firefox 38 ESR based browsers (i.e. New Moon 27, K-Meleon Goanna): Click Here For 38 ESR-based Macintosh browsers (i.e. TenFourFox, Arctic Fox): Click Here For Firefox 45 ESR SSE and 45 ESR based browsers and upwards (not compatible with Quantum): Click Here Introducing the UOC Enforcer UPDATE: The UOC Enforcer is now required if you want to enjoy the full optimizations for your old machine. The UOC Enforcer is a custom "user.js" file that acts as an add-on for the UOC Patch and must be placed into the browser's profile folder and tells the browser to change the "stubborn" entries in the about:config that are hardcoded by the developer, making the UOC Patch work even better. In order to install the UOC Enforcer, you must put the user.js file into your Firefox/New Moon/Pale Moon/Sea Monkey profile folder, that you can usually find at C:\Documents and Settings\User\Application Data\{Your Browser}\{Browser Name}\{Profile Folder} on XP and at C:\Users\{Username}\AppData\Roaming\{Your Browser}\{Browser Name}\{Profile Folder}. You must remember though that the UOC Enforcer doesn't let you change the edits from the about:config, so if you want to change a "stubborn" entry, you must edit the user.js file directly in your profile folder (you can do it with Notepad). UOC Enforcer for Firefox 38 ESR based browsers (i.e. New Moon 27, K-Meleon Goanna): Click Here UOC Enforcer for Firefox 45 ESR based browsers and upwards (i.e. Firefox 45 ESR SSE, SeaMonkey and upwards. Not compatible with Quantum): Click Here A Final Note Please, by all means, test the patch on as many systems as possible! The more the configurations, the better will be. Due to space constraints and lack of money, I don't have access to different systems I can test the patch with, and my Tualatin is the computer I used as a testbed for its development and so, I made it focusing on the hardware I had and currently have. The UOC Patch is not strictly limited to single core systems, but it can be used on any old and slow computer that runs Roytam1's Mozilla forks, it would be interesting to see if it can bring some benefits even on faster systems, or even slower ones: I don't have a Pentium II or an AMD/Intel Socket 7 system to test the patch with, otherwise I would have tried it on those too. There are some extensions I heartedly recommend to use alongside the UOC Patch to make the experience much better. These are: NoScript (I recommend v2.6.9.32 or v2.6.9.27 for New Moon, and v2.9.0.9 for Firefox 45 ESR SSE) Decentraleyes 1.4.2 Bluhell Firewall 2.5.3 UAControl 0.1.3.1.1 (To change the user agent on the fly, per website) uBlock Origin 1.10.0 Vacuum Places Improved 1.2.1 And this one is optional, Youtube 2 Player, a nifty plugin that turns Youtube links into redirects to VLC, so whenever you click on a Youtube link, the video will be loaded automatically in VLC, thus saving resources and CPU cycles. Okay, that's all folks. Now if you want to throw rocks or tomatoes or veggies at me, feel free to do so. I developed this in my free time with a desire of curiosity and experimentation, to see if I can push my old machine to its extreme limit, and so far, at least personally, I'm quite satisfied. But as always, it's up to you to judge whether the UOC Patch is actually useful for your system, or it's an utter piece of garbage. Be aware I'm not responsible of any pandemy, nuclear warfare, space/time continuum and so on caused by your system. I upload the UOC Patch for experimental purposes, and it's provided AS IS. Happy RDD'ing!
  2. This is an updated tutorial of the one cluberti posted here. To get started you need the Windows Performance Tools Kit. Read here how to install it: http://www.msfn.org/board/index.php?showtopic=146919 Now open a command prompt with admin rights and run the following commands: For boot tracing: xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMP Attention: Some users reported that they get a bugcheck (BSOD) when using the DRIVERS flag in the boot trace command. If you get this, use system restore to go back to a working Windows and run the command without DRIVERS xbootmgr -trace boot -traceFlags BASE+CSWITCH+POWER -resultPath C:\TEMPAlso change the name in the command to generate the XML. I've send some dumps to Microsoft, they look at the issue right now. For shutdown tracing: xbootmgr -trace shutdown -noPrepReboot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMPFor Standby+Resume: xbootmgr -trace standby -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMPFor Hibernate+Resume: xbootmgr -trace hibernate -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMPreplace C:\TEMP with any temp directory on your machine as necessary to store the output files All of these will shutdown, hibernate, or standby your box, and then reboot to finish tracing. Once Vista/Server 2008(R2) or Windows 7 does reboot, log back in as necessary and once the countdown timer finishes, you should now have some tracing files in C:\TEMP. If asked, upload or provide the file(s) generated in C:\TEMP (or the directory you chose) on a download share for analysis. Analyses of the boot trace: To start create a summary xml file, run this command (replace the name with the name of your etl file) xperf /tti -i boot_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_boot.xml -a bootNow you see this picture.: You have too look at the timing node. All time values are in ms. The value timing bootDoneViaExplorer shows the time, Windows needs to boot to the desktop. The value bootDoneViaPostBoot is the time (+10s idle detection) which Windows needs to boot completly after finishing all startup applications. those values show you a summary. The MainPathBoot Phase PreSMSS Subphase So if the time takes too long for you, look inside the <PNP> node which driver is loading too slowly. SMSSInit Subphase So if the SMSSInit Phase takes too long, try to get an graphic card driver update. WinLogonInit Subphase If you have too long WinLogonInit Time, open the etl file and scroll to the service graph and look for a long delay. In this example the service SavService (Sophos Anti-Virus\SavService.exe) is part of the Plug and Play group and causes a delay because the service takes too long to start. Try to get an update for the hanging service or remove the software. ExplorerInit Subphase So if the ExplorerInit phase takes too long, make sure you minimize the services which use a lot of CPU power and make sure your AV Tool doesn't hurt too much. If it doesn't change the tool and try a different. The PostBoot Phase If post boot takes too long, reduce the number of running applications at startup with the help of msconfig.exe or AutoRuns. When you have a HDD (no SSD!) and you want to speedup the boot, run the optimization from this guide: http://www.msfn.org/board/index.php?showtopic=140262 Analyses of the shutdown trace: The shutdown is divided into this 3 parts: To generate an XML summary of shutdown, use the -a shutdown action with Xperf: xperf /tti -i shutdown_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_shutdown.xml -a shutdownOpen the XML and you see this: It shows you the most relevant data. <timing shutdownTime="23184" servicesShutdownDuration="1513">The shutdownTime is in this example 23s. Stopping the services takes 1.5s which is fast. Next you have an entry for all sessions. Starting with Vista, all services run in Session 0 (Session 0 Isolation) and each user gets his one Session (1,2,..,n). sessionShutdown sessionID="1" duration="3321">shows the time which it takes to stop all applications which the user is running. In this example it takes 3.3seconds. UserSession Phase sessionShutdown sessionID="0" duration="1513">The value sessionShutdown sessionID="0" shows the servicesShutdownDuration. So you can see which service takes too long to stop. SystemSession Phase In both cases expand the node and look at the shutdownDuration value. It helps you to identify a hanging application are service. KernelShutdown Phase To calculate the time spent in KernelShutdown, subtract the time that is required to shut down the system and user sessions from shutdownTime. In my example: KernelShutdown = 23184 - 3321 - 1513 = 18350 In this case the 18.35 seconds are very slow. In the <interval> you see an entry ZeroHiberFile which takes too long. In this expample the user enabled the Option ClearPageFileAtShutdown under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management to 1. This overrides the hiberbation file with 0 to delete personal data. This causes the huge slowdown. Setting this option to 0 would save 12.64 seconds of shutdown time. That is all you need to analyze slow shutdown issues. Analyses of the Hibernation trace:: To generate the XML, run this command: xperf /tti -i hibernate_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_hibernation.xml -a suspendAnalyses of the Sleep/Resume trace:: xperf /tti -i standby_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_sleep.xml -a suspendOpen the XMLs and look for long BIOS init times and services/application which take very long to suspend and resume. For deeper analysis refer to the Sleep and Hibernate Transitions part of theWindows On/Off Transition Performance Analysis Guide from Microsoft. The pictures Shutdown_cancel.png, Shutdown_picture.png and Boot_MainPathBoot.png were taken from this Windows On/Off Transition Performance Analysis Guide. Read it if you need more information. // Edit: 2010-11-28 Add the explanation of the boot process // Edit: 2010-10-11 added the optimization guide // Edit: 2010-10-09 If you get a BSOD (Bug Check 0x7E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED) while making traces, REMOVE ALL USB DEVICES and reboot! When making a new trace remove the DRIVERS flag from the command line! // Edit: 2010-02-04 Added the -noPrepReboot command at shutdown tracing to prevent the preparatory reboot during a shutdown/rebootCycle trace. Usually, the reboot is required to ensure a consistent machine state before the first shutdown if multiple traces are being taken. // Edit: 2010-05-08 Added the link to the Visual Studio 2010 Diagnostic Tool as alternative download to get the Windows Performance Toolkit Installers. Added some pictures.
  3. This is an updated tutorial of my Windows 7 here. To get started you need the Windows Performance Tools Kit. Read here how to install it: http://www.msfn.org/board/index.php?showtopic=146919 Now open a command prompt with admin rights and run the following commands: For boot tracing: xbootmgr -trace boot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMPNote, in Windows 8 it is safe to use the DRIVERS flag, the Windows 7 bug is fixed in Windows 8. For shutdown tracing: xbootmgr -trace shutdown -noPrepReboot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMPFor Standby+Resume: xbootmgr -trace standby -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMPFor Hibernate+Resume: xbootmgr -trace hibernate -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMPreplace C:\TEMP with any temp directory on your machine as necessary to store the output files All of these will shutdown, hibernate, or standby your box, and then reboot to finish tracing. After you login to your PC, the new startscreen is shown and you have to click to the desktop to see countdown timer. Again, wait until the timer finishes. Afetr you did this you should now have some tracing files in C:\TEMP. Analyses of the boot trace: To start create a summary xml file, run this command (replace the name with the name of your etl file) xperf /tti -i boot_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_boot.xml -a bootNow you see this picture.: You have too look at the timing node. All time values are in ms. The value timing bootDoneViaExplorer shows the time, Windows needs to boot to the desktop. The value bootDoneViaPostBoot is the time (+10s idle detection) which Windows needs to boot completly after finishing all startup applications. those values show you a summary. The MainPathBoot Phase PreSMSS Subphase So if the time takes too long for you, look inside the <PNP> node which driver is loading too slowly. SMSSInit Subphase So if the SMSSInit Phase takes too long, try to get an graphic card driver update. WinLogonInit Subphase If you have too long WinLogonInit Time, open the etl file and scroll to the service graph and look for a long delay. In this example the service SavService (Sophos Anti-Virus\SavService.exe) is part of the Plug and Play group and causes a delay because the service takes too long to start. Try to get an update for the hanging service or remove the software. ExplorerInit Subphase So if the ExplorerInit phase takes too long, make sure you minimize the services which use a lot of CPU power and make sure your AV Tool doesn't hurt too much. If it doesn't change the tool and try a different. The PostBoot Phase If post boot takes too long, reduce the number of running applications at startup with the help of msconfig.exe or AutoRuns. if possible, you should always use the new Fast Startup/ hybrid Boot of Windows 8. At the end of this guide you'll learn how to analyze this new mode. Analyses of the shutdown trace: The shutdown is divided into this 3 parts: To generate an XML summary of shutdown, use the -a shutdown action with Xperf: xperf /tti -i shutdown_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_shutdown.xml -a shutdownOpen the XML and you see this: It shows you the most relevant data. <timing shutdownTime="23184" servicesShutdownDuration="1513">The shutdownTime is in this example 23s. Stopping the services takes 1.5s which is fast. Next you have an entry for all sessions. Starting with Vista, all services run in Session 0 (Session 0 Isolation) and each user gets his one Session (1,2,..,n). sessionShutdown sessionID="1" duration="3321">shows the time which it takes to stop all applications which the user is running. In this example it takes 3.3seconds. UserSession Phase sessionShutdown sessionID="0" duration="1513">The value sessionShutdown sessionID="0" shows the servicesShutdownDuration. So you can see which service takes too long to stop. SystemSession Phase In both cases expand the node and look at the shutdownDuration value. It helps you to identify a hanging application are service. KernelShutdown Phase To calculate the time spent in KernelShutdown, subtract the time that is required to shut down the system and user sessions from shutdownTime. In my example: KernelShutdown = 23184 - 3321 - 1513 = 18350 In this case the 18.35 seconds are very slow. In the <interval> you see an entry ZeroHiberFile which takes too long. In this expample the user enabled the Option ClearPageFileAtShutdown under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management to 1. This overrides the hiberbation file with 0 to delete personal data. This causes the huge slowdown. Setting this option to 0 would save 12.64 seconds of shutdown time. That is all you need to analyze slow shutdown issues. Analyses of the Hibernation trace:: To generate the XML, run this command: xperf /tti -i hibernate_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_hibernation.xml -a suspendAnalyses of the Sleep/Resume trace:: xperf /tti -i standby_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_sleep.xml -a suspendOpen the XMLs and look for long BIOS init times and services/application which take very long to suspend and resume. Windows 8 includes a new boot mode called Fast Startup or Hybrid Boot. If this boot mode is slow, you have to run this command to trace the slowness: xbootmgr -trace fastStartup -noPrepReboot -traceFlags BASE+CSWITCH+DRIVERS+POWER -resultPath C:\TEMPI've already explained how this mode works. First Windows shuts down the users, next Windows hibernates the kernel with all drivers and the services. Next the PC shuts down. Now Windows boots again, read the hibernation file and resumes all services and drivers and next you go to the Logon screen. So we now need to view all 3 actions. So first look is the closing of apps and logging off the users takes too long. Create the shutdown XML with this command: xperf -i fastStartup_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_shutdown.xml -a shutdownOpen it and you'll see this: Note, that the file only shows the logoff of the user sessions. Here check which programs take long to close. The FlushVolume is writing open files/cache to the HDD. Next, we must look if the hibernation is slowly. To generate the XML run this: xperf -i fastStartup_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_hibernation.xml -a suspendOpen it and you'll see this: Now the same applies like Hibernation. Look which services or drivers take a long time to suspend. Also note, that those values are in µs! If those 2 steps are fine, we must look at the new Startup. To generate the XML run this: xperf -i fastStartup_BASE+CSWITCH+DRIVERS+POWER_1.etl -o summary_Boot.xml -a bootOpen it and you'll see this: When you compare it to the normal boot, you see some differences. The PreSMSS and SMSSInit Subphases are gone. This is replaced with SystemResume. If this takes a very long time, open again the summary_hibernation.xml and look for devices are services which take long time to resume. The rest of the boot is the same like the normal boot. If WinLogonInit are long, check the Group Policies and if you're restoring of network connections. And if PostExplorerPeriod is long, you also start too many desktop programs or your new Windows 8 apps take too long to load the data to show in the live tiles. I hope, this helps you to fix your Performance issues with Windows 8. The pictures Shutdown_cancel.png, Shutdown_picture.png and Boot_MainPathBoot.png were taken from this Windows On/Off Transition Performance Analysis Guide. Read it if you need more information.
  4. For win7 existed the web of Black Viper which had an useful list of services that could be disabled. Even one guy made this awesome program that applied those configurations. Is there any list (with its reg file) or software that has predetermined list to disable services for windows 10? Thanks you
×
×
  • Create New...