Hallo

ich habe vor kurzem meine Access Datenbank mit mySQL Version 4.1.14 abgelöst. (vorher noch nie mySQL selbst eingerichtet, habe keine Ahnung vom konfigurieren)
seit diesem Wechsel ist mein Programm, das ich mit PHP Version 4.3.3 geschrieben habe total langsam.

mit Access hat der Seitenaufbau maximal eine halbe Sekunde gedauert. jetzt mit mySQL dauert der Seitenaufbau ~3 Sekunden.
ich benutze, soweit ich weiss einen P3 700 MHZ mit 256 SDRAM.

wäre nett, wenn mir jemand helfen könnte

hm ein kleiner Nachtrag. mySQL ist wohl nur langsam, wenn Outer/InnerJoins in der Abfrage sind. bei normalen SELECT's ist die Geschwindigkeit wohl ganz normal.

gibt es dafür irgendwelche Einstellungen in den Konfigurationsdateien? o_O

Hallo,

vesuch mal, eine andere Storage-Engine einzustellen. Nach meiner Erfahrung ist die MyISAM bei Abfragen aus Java (JDBC) heraus wesentlich schneller als die InnoDB-Engine, die, so glaube ich, standardmäßig verwendet wird...

CREATE TABLE ... (
...
) ENGINE=MyISAM;

Wäre über Info dankbar, ob das so richtig ist bzw. etwas gebracht hat ;o)

Gruß Moxx

Morgen.

ich hab jetzt mal alle Tabellen mit "ALTER TABLE `tabelle` ENGINE=MyISAM" geupdated. das hat auch funktioniert, schneller wurde das ganze jedoch nicht. ich bin mir nicht ganz sicher, aber ich glaube, dass MyISAM schon eingestellt war. denn ich benutze zur Verwaltung von mySQL den phpmyAdmin und da war MyISAM beim "Table type" bereits ausgewält.

woran könnte es denn noch liegen? :/

Ich hatte mal so ein Problem nach der Umstellung auf WAMMP2, wenn ich mich richtig erinnere war da in der C:\WINDOWS\my.ini eine Zeile mit Debug-Modus, die hat enorm gebremst.

mit Debug hab ich jetzt nix in der .ini gefunden. ich poste mal meine Config

Code :

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158

# Example MySQL config file for large systems. # # This is for a large system with memory = 512M where the system runs mainly # MySQL. # # You can copy this file to # /etc/my.cnf to set global options, # mysql-data-dir/my.cnf to set server-specific options (in this # installation this directory is /usr/local/var) or # ~/.my.cnf to set user-specific options. # # In this file, you can use all long options that a program supports. # If you want to know which options a program supports, run the program # with the "--help" option.   # The following options will be passed to all MySQL clients [client] #password   = your_password port        = 3306 socket      = /tmp/mysql.sock   # Here follows entries for some specific programs   # The MySQL server [mysqld] port        = 3306 socket      = /tmp/mysql.sock skip-locking key_buffer = 256M max_allowed_packet = 1M table_cache = 256 sort_buffer_size = 1M read_buffer_size = 1M read_rnd_buffer_size = 4M myisam_sort_buffer_size = 64M thread_cache = 8 query_cache_size= 16M # Try number of CPU's*2 for thread_concurrency thread_concurrency = 8   # Don't listen on a TCP/IP port at all. This can be a security enhancement, # if all processes that need to connect to mysqld run on the same host. # All interaction with mysqld must be made via Unix sockets or named pipes. # Note that using this option without enabling named pipes on Windows # (via the "enable-named-pipe" option) will render mysqld useless! # #skip-networking   # Replication Master Server (default) # binary logging is required for replication log-bin   # required unique id between 1 and 2^32 - 1 # defaults to 1 if master-host is not set # but will not function as a master if omitted server-id   = 1   # Replication Slave (comment out master section to use this) # # To configure this host as a replication slave, you can choose between # two methods : # # 1) Use the CHANGE MASTER TO command (fully described in our manual) - #    the syntax is: # #    CHANGE MASTER TO MASTER_HOST=<host>, MASTER_PORT=<port>, #    MASTER_USER=<user>, MASTER_PASSWORD=<password> ; # #    where you replace <host>, <user>, <password> by quoted strings and #    <port> by the master's port number (3306 by default). # #    Example: # #    CHANGE MASTER TO MASTER_HOST='125.564.12.1', MASTER_PORT=3306, #    MASTER_USER='joe', MASTER_PASSWORD='secret'; # # OR # # 2) Set the variables below. However, in case you choose this method, then #    start replication for the first time (even unsuccessfully, for example #    if you mistyped the password in master-password and the slave fails to #    connect), the slave will create a master.info file, and any later #    change in this file to the variables' values below will be ignored and #    overridden by the content of the master.info file, unless you shutdown #    the slave server, delete master.info and restart the slaver server. #    For that reason, you may want to leave the lines below untouched #    (commented) and instead use CHANGE MASTER TO (see above) # # required unique id between 2 and 2^32 - 1 # (and different from the master) # defaults to 2 if master-host is set # but will not function as a slave if omitted #server-id       = 2 # # The replication master for this slave - required #master-host     =   <hostname> # # The username the slave will use for authentication when connecting # to the master - required #master-user     =   <username> # # The password the slave will authenticate with when connecting to # the master - required #master-password =   <password> # # The port the master is listening on. # optional - defaults to 3306 #master-port     =  <port> # # binary logging - not required for slaves, but recommended #log-bin   # Point the following paths to different dedicated disks #tmpdir     = /tmp/     #log-update     = /path-to-dedicated-directory/hostname   # Uncomment the following if you are using BDB tables #bdb_cache_size = 64M #bdb_max_lock = 100000   # Uncomment the following if you are using InnoDB tables #innodb_data_home_dir = /usr/local/var/ #innodb_data_file_path = ibdata1:10M:autoextend #innodb_log_group_home_dir = /usr/local/var/ #innodb_log_arch_dir = /usr/local/var/ # You can set .._buffer_pool_size up to 50 - 80 % # of RAM but beware of setting memory usage too high #innodb_buffer_pool_size = 256M #innodb_additional_mem_pool_size = 20M # Set .._log_file_size to 25 % of buffer pool size #innodb_log_file_size = 64M #innodb_log_buffer_size = 8M #innodb_flush_log_at_trx_commit = 1 #innodb_lock_wait_timeout = 50   [mysqldump] quick max_allowed_packet = 16M   [mysql] no-auto-rehash # Remove the next comment character if you are not familiar with SQL #safe-updates   [isamchk] key_buffer = 128M sort_buffer_size = 128M read_buffer = 2M write_buffer = 2M   [myisamchk] key_buffer = 128M sort_buffer_size = 128M read_buffer = 2M write_buffer = 2M   [mysqlhotcopy] interactive-timeout

habe eigentlich nix verändert, das is die ganz normale Standard "my-large.ini2