Results 1 to 3 of 3

Thread: What does the "Page File Usage History" chart measure.

  1. #1
    Join Date
    Oct 2005
    Posts
    67

    What does the "Page File Usage History" chart measure.

    I am having a Windows XP Pro system. I use the software to convert some movies file. I am trying to convert AVI files to DVD. The cpu usage goes to 100% at the time of conversion. I am using a Dual Core processor. So I expect that the usage must not go to 100%. I am having only 1GB ram in the system. Does that is causing performance break. The page file on the same is around 1GB. I think the system requires more ram.

  2. #2
    Join Date
    Sep 2004
    Posts
    156
    Yes you need more ram. And converting a video is a resource intensive job. The bigger the video is the more hardware it needs. You must get more on 1GB stick and add that to your system. If your video size is bigger than 500MB then the converting process takes a long time. I convert videos from 100MB to 400 and it takes around 15 to 20 minutes with full cpu utilization.

  3. #3
    Join Date
    Sep 2004
    Posts
    150
    Try running Disk Defragmentation for a while. It will clean the data and arrange it more properly. This gives you easy accessibility and offers a much better way to use system resources. I too agree that video conversion is a resource intensive job. The processor is fully utilized that means your system performance needs more better hardware.

Similar Threads

  1. Replies: 3
    Last Post: 31-12-2013, 10:36 AM
  2. Replies: 2
    Last Post: 17-01-2012, 01:21 PM
  3. Replies: 4
    Last Post: 12-02-2011, 07:10 AM
  4. "History" and "Recent" Folders--how to delete contents ?
    By troop in forum Windows XP Support
    Replies: 7
    Last Post: 13-06-2009, 01:53 PM
  5. Replies: 1
    Last Post: 06-11-2007, 02:18 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,711,646,155.46804 seconds with 17 queries