Oracle 10g Windows平台.ppt

Database Architecture Agenda Oracle Database 10g on Windows architecture 64-bit development landscape Migration compatibility (32-bit to 64-bit) Future directions conclusion Customer case study: Intel Architecture: Thread Model Unlike UNIX ports of Oracle Database 10g, Oracle Database 10g on Windows is implemented as a single operating system process. Typical “processes” such as PMON and LGWR have been converted to native Windows threads running in the single large Oracle process. One process exists per instance on a Windows machine.  Architecture: Thread Model Architecture: Thread Model Internally, relatively few code changes are required to implement the thread model. The SGA and PGAs are allocated differently and threads are used instead of processes, but very little else needs to change. As a result, it’s easy to maintain and port the database while at the same time preserving it’s inherent stability, features, and performance. Architecture: Thread Model Thread model benefits: Faster context switches Decreased memory usage Quicker connection times Perceived as a more “native” implementation since it uses threads versus processes No changes required for client applications Architecture: File I/O Full support for 64-bit file I/O enables very large files to be used by Oracle Database 10g on Windows There are no 2GB or 4GB limitations on database file sizes. The maximum size for an entire database on Windows is 4 petabytes (64K files x 16K bytes/block x 4M blocks/file). Architecture: File I/O Async file I/O is built into Windows and Oracle Database 10g supports async I/O to all types of files, assuming that the portable code layers utilize async I/O. No limits on the number of files in a single database except those already imposed by Oracle portable code (around 64K files). Raw files are fully supported. They are better performing than file system files, but are harder to manage. Architecture: Tuning Both CPU affinities and thread priorities can be set