AboutPeter Choi Expertise I am a senior Oracle DBA, PeopleSoft Administrator and Project Manager with
10+ years experience. I have been working with PeopleSoft (HRMS 5, 7, 7.x and
8.9), Oracle RDBMS (7.3 - 11gR1) on various Unix and Windows platforms, and some Oracle Application Server (9i/10gR2). I also have experience with the configuration and administration of BEA`s Tuxedo and WebLogic for PeopleSoft 8.x.
Question at present iam using
1.HP make
2.Dual core intelxenon@3GHZ processor
3.6MB L2cache
4.667MHZS FSB
5.2 GB RAM
6.250 GB SATA Harddisk
above are the specification which iam using for 10gserver,
in IDLE state PF usage is nearly 1.30GB,when my application starts running(it post the data into server with speed of 16000records/sec ) the pf usage is 1.88GB.Gradually posting speed decreases.Could u suggest is there any specification problem,to Have a better performance what i had to do ?Expecting quick response
Answer Hi Kalyan,
Which version of the OS are you running? Is it 32-bit or 64-bit version?
Three things to take a look at:
1. Memory
Your page file (PF) usage is an extension of your memory. It is a variable amount of hard drive space that is dedicated to your total system memory. When your free RAM is low, the computer will start using this space to store RAM instructions. Because hard drive access is much slower than that of RAM, this can reduce performance - but reduces the risk of your computer locking up due to low amounts of free RAM. The page file is also referred to as 'virtual memory' or the 'swap file'.
Take a look at your SGA allocation. (on sqlplus, you can type the command SHOW SGA). This will show you how you have allocated memory to your system. If you've under allocated, Oracle will swap out to disk, reducing your performance. Over allocating to the SGA will also cause swapping (if you try to allocate more than what physical memory that you have).
2. Posting data to database
There are two types of transactions that you could be incurring: INSERT, UPDATE and DELETE. If you're doing a sequence INSERT, you may want to consider dropping your index before allowing the insert. As you add larger volumes to the tables, Oracle needs to balance out the index structure. The more indicies you have, the more processing it will consume. UPDATES and DELETES are selective, and depending on the query, if you are performing full table scans (FTS) and you have a very large table, then performance will decrease. You may need to analyze your queries to make sure that they are optimized (run an EXPLAIN PLAN; reference: http://www.adp-gmbh.ch/ora/explainplan.html). If you're using default Oracle 10gR2 settings, you might want to check if your table statistics are up to date. (Reference: http://www.oradev.com/create_statistics.jsp)
3. Other processes running on your server.
If you're multitaksing on that server, then your resource will be reduced as you run your posting to the database. One option is to stop or shutdown non-critical programs/processes.
MONITOR your CPU, RAM and DISK activity. PF, while is associated to RAM, only gives you a partial symptom of the problem. I suspect that your process is I/O intensive (read/write to database). You may need to ensure that there are regular commit points in your posting process.
