![]() ![]() For a full implementation of in-memory tables a primary key is mandatory, however by definition the HISTORY table does not have a primary key. Although the differences between hash and standard indexes are out of scope for this guide it is recommended to become familiar with the architecture as a key difference is the requirement to create all of the tables memory requirements ‘up-front’ with too little or too much memory impacting performance and therefore monitoring of the memory configuration usage is essential for workloads operating on In-memory databases. In-memory tables are implemented with hash indexes with no additional indexes created during the schema creation. The key difference with the In-memory schema from the on-disk database is the organization of the tables. If you have a significantly larger core/Hyper-Thread count on your Database Server then also installing HammerDB locally on this server as well to run the schema build can take advantage of the higher core count to run the build more quickly. You should set this value to either the number of warehouses you are going to create (You cannot set the number of virtual users higher than the number of warehouses value) or the number of cores/Hyper-Threads on your Load Generation Server. The Virtual Users to Build Schema is the number of Virtual Users to be created on the Load Generation Server that will complete your multi-threaded schema build. You should set this value to number of warehouses you have chosen for your test. The Number of Warehouses is selected by a listbox. Selecting this option also partitions the Orders and History tables. Using partitioning enables scalability for high performance schemas and should be considered with using a separate tablespace for the Order Line table. When more than 200 warehouses are selected this option uses Oracle partitioning to divide the Order Line table into partitions of 100 warehouses each. When Hash Clusters are enabled table locks are also disabled with the command "ALTER TABLE XXX DISABLE TABLE LOCK" and these locks will need to be re-enabled to drop the schema when required. ![]() These options can provide additional levels of scalability on high performance systems where contention is observed however will not provide significant performance gains on entry level systems. When Partitioning is selected this option enables the building of static tables as single table hash clusters and also disables table locks. When selected this option means that the Oracle Service Name should be a TimesTen Data Source Name and will grey out non-compatible options. The TPROC-C temporary tablespace is the temporary tablespace that already exists in the database to be used by the TPROC-C User. Where a different cache and blocksize is used 16k is recommended. For high performance schemas this gives the option of using both a separate tablespace and memory cache for the order line table with a different block size. If this is selected then the option to select a different tablespace for the Order Line table only becomes active. If the “Number of Warehouses” as described below is set to 200 or more then the “Partition Order Line Table” option becomes active. The tablespace must have sufficient free space for the schema to be created. The TPROC-C default tablespace is the tablespace that will be the default for the TPROC-C user and therefore the tablespace to be used for the schema creation. You will need to remember the TPROC-C user name and password for running the TPROC-C driver script after the schema is built. The TPROC-C user password is the password to be used for the TPROC-C user you create and must adhere to the standard rules for Oracle user password. You may if you wish run the schema creation multiple times and have multiple TPROC-C schemas created with ownership under a different user you create each time. This user can have any name you choose but must not already exist and adhere to the standard rules for naming Oracle users. The TPROC-C user is the name of a user to be created that will own the TPROC-C schema. The system user already exists in all Oracle databases and has the necessary permissions to create the TPROC-C user. The system user password is the password for the “system” user you entered during database creation. The “system” user or a user with system level privileges The Oracle Service Name is the service name that your load generation server will use to connect to the database running on the SUT database server. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |