Closed firebird-automations closed 18 years ago
firebird-automations
commented
18 years ago Commented by: Alice F. Bird (firebirds)
Date: 2006-04-24 17:11 Sender: rrokytskyy Logged In: YES user_id=356832
What about transactions? Did you run in auto-commit mode? If not, after how many inserts did you commit?
firebird-automations
commented
18 years ago Commented by: Alice F. Bird (firebirds)
Date: 2006-04-24 17:05 Sender: iglezias Logged In: YES user_id=762593
Another information: - We used JDK1.5. - The problem ocurred with both 1.5.3(release) and 2.0.0- Beta2 of FB Server - we used the following JDBC versions: * Jaybird 1.5.6 for JDK 1.4 * Jaybird 2.0.1 for JDK 1.5
firebird-automations
commented
18 years ago Commented by: Roman Rokytskyy (rrokytskyy)
No additional comments have been provided. Please re-open when needed.
firebird-automations
commented
18 years ago
Submitted by: iglezias (iglezias)
Assigned to: Roman Rokytskyy (rrokytskyy)
SFID: 1475575# Submitted By: iglezias
In a project I worked at SERPRO-Brasil, for ReceitaFederal-Brasil, we should put a great amount of data into a FB database, loading them from a TextFile source. It was made using Java. In our tests, we saw that after about 40min (some cases after 1hour), the JVM stoped (freezing) (the Firebird server still worked fine...we made tests), and we discoverd that the problem was the Firebird-JDBCDriver. We changed the project to work with PostgreSQL, and all worked fine (all done in about 50hours of processing).
The program consists, basicaly, of a 3000 inserts per second process (at our computer, pIV-HT, 3.2GHz, 1GbRAM). At each insert, some small and fast selects were made too. During the processing (using FB), there was no great "memory using" variation, and FB got about 70% of CPU (30% for JVM). The resultant Database (PostgreSQL), after the 50hours processing, has 16Gbytes of size.