SUN hardware benchmark

SUN Enterprise 250 / 248 MHZ / 256 MB
[Feb 14 10:01:48 UTC] Automatic processor type detection found an UltraSPARC-II processor.
[Feb 14 10:01:48 UTC] RC5-72: using core #5 (AnBe 2-pipe).
[Feb 14 10:02:07 UTC] RC5-72: Benchmark for core #5 (AnBe 2-pipe) 0.00:00:16.52 [501,916 keys/sec]
[Feb 14 10:02:26 UTC] OGR-P2: Benchmark for core #0 (GARSP 6.0) 0.00:00:16.69 [2,823,340 nodes/sec]

SUN Ultra 10 / 333 MHz / 512 MB
[Feb 14 09:59:21 UTC] Automatic processor type detection found an UltraSPARC-IIi processor.
[Feb 14 09:59:21 UTC] RC5-72: using core #5 (AnBe 2-pipe).
[Feb 14 09:59:39 UTC] RC5-72: Benchmark for core #5 (AnBe 2-pipe) 0.00:00:16.15 [685,418 keys/sec]
[Feb 14 09:59:58 UTC] OGR-P2: Benchmark for core #0 (GARSP 6.0) 0.00:00:16.84 [3,854,463 nodes/sec]

SUN Ultra 10 / 440 MHZ / 512 MB
[May 01 05:29:15 UTC] Automatic processor type detection found an UltraSPARC-IIi processor.
[May 01 05:29:15 UTC] RC5-72: using core #5 (AnBe 2-pipe).
[May 01 05:29:33 UTC] RC5-72: Benchmark for core #5 (AnBe 2-pipe) 0.00:00:16.23 [908,269 keys/sec]
[May 01 05:29:53 UTC] OGR-P2: Benchmark for core #0 (GARSP 6.0) 0.00:00:16.91 [5,123,975 nodes/sec]

SUN Blade 100 / 500 MHz / 512 MB
[Feb 14 09:59:21 UTC] Automatic processor type detection found an UltraSPARC-IIe processor.
[Feb 14 09:59:21 UTC] RC5-72: using core #5 (AnBe 2-pipe).
[Feb 14 09:59:39 UTC] RC5-72: Benchmark for core #5 (AnBe 2-pipe) 0.00:00:16.15 [1,101,418 keys/sec]
[Feb 14 09:59:58 UTC] OGR-P2: Benchmark for core #0 (GARSP 6.0) 0.00:00:16.84 [5,231,463 nodes/sec]

SUN Blade 1000 / 750 MHZ / 1 GB
[May 01 05:34:12 UTC] Automatic processor type detection found an UltraSPARC-III processor.
[May 01 05:34:12 UTC] RC5-72: using core #5 (AnBe 2-pipe).
[May 01 05:34:31 UTC] RC5-72: Benchmark for core #5 (AnBe 2-pipe) 0.00:00:16.21 [1,557,063 keys/sec]
[May 01 05:34:50 UTC] OGR-P2: Benchmark for core #0 (GARSP 6.0) 0.00:00:16.59 [8,394,930 nodes/sec]

SUN Fire 210 / 1 GHZ / 4 GB
[Feb 14 10:15:19 UTC] Automatic processor type detection found an UltraSPARC-IIIi processor.
[Feb 14 10:15:20 UTC] RC5-72: using core #5 (AnBe 2-pipe).
[Feb 14 10:15:38 UTC] RC5-72: Benchmark for core #5 (AnBe 2-pipe) 0.00:00:16.06 [2,079,802 keys/sec]
[Feb 14 10:15:57 UTC] OGR-P2: Benchmark for core #0 (GARSP 6.0) 0.00:00:16.43 [11,217,790 nodes/sec]

SUN Fire 240 / 1 GHZ / 4 GB
[Feb 14 10:05:39 UTC] Automatic processor type detection found an UltraSPARC-IIIi processor.
[Feb 14 10:05:39 UTC] RC5-72: using core #5 (AnBe 2-pipe).
[Feb 14 10:05:58 UTC] RC5-72: Benchmark for core #5 (AnBe 2-pipe) 0.00:00:16.61 [2,088,402 keys/sec]
[Feb 14 10:06:17 UTC] OGR-P2: Benchmark for core #0 (GARSP 6.0) 0.00:00:16.64 [11,263,969 nodes/sec]

MySQL notes

#######
Creating MySQL database on Linux system

1. I assume that you are working from your account and not the root. Start a terminal session and become the superuser (Type su at the prompt and then enter the root password).
2. Now we’ll access the MySQL server. Type:

mysql -u root -p

The system prompts for the MySQL root password that you set up in Installing MySQL on Linux. (Note: This is not the Linux root password but the MySQL root password). Enter the password, which is not displayed for security reasons.
Once you are successfully logged in, the system prints a welcome message and displays the mysql prompt … something like

Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 1 to server version: 3.22.32

Type ‘help’ for help.

mysql>

3. Now we are ready for creating the employees database. Issue the command:

create database employees;

(Note: The command ends with a semi-colon)

4. An important point to note is that this database is created by the root and so will not be accessible to any other user unless permitted by the root. Thus, in order to use this database from my account (called manish), I have to set the permissions by issuing the following command:

GRANT ALL ON employees.* TO manish@localhost IDENTIFIED BY “eagle”

The above command grants my account (manish@localhost) all the permissions on employees database and sets my password to eagle. You should replace manish with your user name and choose an appropriate password.
5. Close the mysql session by typing quit at the prompt. Exit from superuser and come back to your account. (Type exit).
6. To connect to MySQL from your account, type:

mysql -u user_name -p

Type in the password when prompted. (This password was set by the GRANTS ALL… command above) . The system displays the welcome message once you have successfully logged on to MySQL. Here is how your session should look like:

[manish@localhost manish]$ mysql -u manish -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 3 to server version: 3.22.32

Type ‘help’ for help.

mysql>

7. Typing the command SHOW DATABASES; will list all the databases available on the system. You should get a display similar to:

mysql> SHOW DATABASES;
+—————-+
| Database |
+—————-+
| employees |
| mysql |
| test |
+—————-+
3 rows in set (0.00 sec)

8. Enter quit at the mysql> prompt to come out of the mysql client program.

########
LOAD DUMP

After you have dumped out your data into a file as described here, FTP or scp that dump file to the home directory (/) on our system.

Once you have uploaded the dump file to your account here, get a shell prompt on our system using telnet or ssh.

Now import the dump file into MySQL by typing all the following on 1 single line at the shell prompt:

mysql -p -h DBSERVER dbname < dbname.sql The above assumes that your database name on our system is "dbname" and the dumpfile that you uploaded was named "dbname.sql". Replace those with your correct database name and dumpfile filename. Also replace DBSERVER with your correct database server name. ###### SET OLD PASSWORD Reset the password to pre-4.1 style for each user that needs to use a pre-4.1 client program. This can be done using the SET PASSWORD statement and the OLD_PASSWORD() function: mysql> SET PASSWORD FOR ‘some_user’@’some_host’ = OLD_PASSWORD(‘newpwd’);
mysql> FLUSH PRIVILEGES;

Substitute the password you want to use for “newpwd” in the preceding examples. MySQL cannot tell you what the original password was, so you’ll need to pick a new one.

######
Drop database

Definition: The drop database command is used when you no longer need one of the SQL databases on your server. It will remove it permanently. It is phrased as: drop database [DatabaseName];
Examples: This will remove the database ‘Dresses’ from the MySQL server:

mysql> drop database Dresses;