| 
                        February 01, 2011 Mark Wielaard: New GPG key. 
Finally created a new GPG key using gnupg. The old one was a DSA/1024 bits one and 8 years old. The new one is a RSA/2048 bits one. I will use the new one in the future to sign any release tarballs I might create. pub 2048R/57816A6A 2011-01-29 Key f... More » 
                        February 01, 2011 Andrew Hughes: [SECURITY] IcedTea6 1.7.8, 1.8.5, 1.9.5 Released!. 
We are pleased to announce a new set of security releases, IcedTea6 1.7.8, IcedTea6 1.8.5 and IcedTea6 1.9.5.
This update contains the following security updates:
 
The IcedTea project provides a harness to build the source code from OpenJDK6 u... More » 
                    October/2025 | Sun | Mon | Tue | Wed | Thu | Fri | Sat |  
|  |  |  | 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 |  | 
 |  | 
                      
                      
                        
                        
                      
                      
                 
                       				        JPA Performance, Don't Ignore the Database					                      
                    
                    
                 
JPA Performance, Don't Ignore the Database
Database Schema
Good Database schema design is important for performance. One of             the most basic optimizations is to design your tables to take as little             space on the disk as possible , this makes disk reads faster and         uses less memory for query processing. 
Data Types
You should use             the smallest data types possible, especially for indexed fields.         The smaller your data types, the more indexes (and data) can fit into a         block of memory, the faster your queries will be.
Normalization
Database Normalization eliminates redundant data, which usually makes         updates faster since there is less data to change. However a Normalized         schema causes joins for queries, which makes queries slower,         denormalization speeds retrieval. More normalized schemas are better         for applications involving many transactions, less normalized are         better for reporting types of applications.  You should normalize         your schema first, then de-normalize later.  Applications often         need to mix the approaches, for example use a partially normalized         schema, and duplicate, or cache, selected columns from one table in         another table. With JPA O/R mapping you can use the @Embedded         annotation for denormalized columns to specify a persistent field whose         @Embeddable         ty... 
 
Date: August, 28 2009Url:  http://www.java.net/blog/caroljmcdonald/archive/2009/08/28/jpa-performance-dont-ignore-database-0
 
 
 Others News |