Skip to main content

ArrayList vs LinkedList vs HashSet Performance Comparision



Conclusions

Inserting & Reading sequentially from Collection prefer LinkedList/ArrayList

Inserting & Reading/Deleting by Search/equals from Collection prefer HashSet

Inserting, ArrayList & LinkedList performs best while HashSet takes double the time

Reading, HashSet performs best while ArrayList & LinkedList are marginally less

Deleting, HashSet performs 10 times better than ArrayList & ArrayList performs 4 times better than LinkedList. LinkedList is slow because of sequencial search

Bottom line : unless you are not going to iterate using for(Integer i : list ) then prefer HashSet


Inserting/Reading/Deleting integer's from zero till count

JDK7Collectionactioncounttime ms
ArrayListInsert1000/1
LinkedListInsert1000/1
HashSetInsert1000/1
ArrayListInsert100005
LinkedListInsert100004
HashSetInsert100007
ArrayListInsert10000011
LinkedListInsert10000011
HashSetInsert10000021
ArrayListGet/Read1000
LinkedListGet/Read1000
HashSetGet/Read1000
ArrayListGet/Read100004
LinkedListGet/Read100003
HashSetGet/Read100004
ArrayListGet/Read10000010
LinkedListGet/Read10000010
HashSetGet/Read1000009

JDK6Collectionactioncounttime ms
ArrayListInsert1000/1
LinkedListInsert1000/1
HashSetInsert1000/1
ArrayListInsert100005
LinkedListInsert100004
HashSetInsert100007
ArrayListInsert10000012
LinkedListInsert10000011
HashSetInsert10000017
ArrayListGet/Read1000
LinkedListGet/Read1000
HashSetGet/Read1000
ArrayListGet/Read100005
LinkedListGet/Read100003
HashSetGet/Read100004
ArrayListGet/Read10000010
LinkedListGet/Read10000010
HashSetGet/Read1000009

JDK6Collectionactioncounttime ms
ArrayListinsert & remove 25%100000336
LinkedListGet/Read1000001188
HashSetGet/Read10000025

JDK7Collectionactioncounttime ms
ArrayListinsert & remove 25%100000337
LinkedListGet/Read1000001208
HashSetGet/Read10000032

Environment

MacBook Pro

Processor 2.3 GHz Intel Core i7

Memory 16 GB 1600 MHz DDR3

Software OS X 10.8 (12A269)

Comments

Popular posts from this blog

Access multiple Databases in JPA

According to JPA specification we can define multiple "persistence-unit" elements (i.e. like below) in persistence.xml file and can easily refer them inside Dao layers as this. public class PolarDaoImpl {     @PersistenceContext(unitName="PolarPU")     protected EntityManager entityManager; -- } public class BearDaoImpl {     @PersistenceContext(unitName="BearPU")     protected EntityManager entityManager; -- } Checkout sample persistence.xml <?xml version="1.0" encoding="UTF-8"?> <persistence version="2.0" xmlns="http://java.sun.com/xml/ns/persistence" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/persistence http://java.sun.com/xml/ns/persistence/persistence_2_0.xsd">     <!-- Database 1 -->     <persistence-unit name="PolarPU" transaction-type="RESOURCE_LOCAL">         <

JPA 2 new feature @ElementCollection explained

@ElementCollection is new annotation introduced in JPA 2.0, This will help us get rid of One-Many and Many-One shitty syntax. Example 1: Stores list of Strings in an Entity @Entity public class Users implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @ElementCollection     private List<String> certifications = new ArrayList <String> ();     public Long getId() {         return id;     }     public void setId(Long id) {         this.id = id;     }     public List <String> getCertifications() {         return certifications;     }     public void setCertifications(List <String> certifications) {         this.certifications = certifications;     } .. }         Users u = new Users();         u.getCertifications().add("Sun Certified Java Programmer");         em.persist(u); Generated Tables    Users    Co

Reuse JPA Entities as DTO

Note : Major design advantages of JPA Entities are they can detached and used across tiers and networks and later can by merged. Checkout this new way of querying entities in JPA 2.0 String ql = " SELECT new prepclass2.Employee (e.firstname, e.lastname) FROM Employee e "; List<Employee> dtos = em.createQuery(ql).getResultList(); The above query loads all Employee entities but with subset of data i.e. firstname, lastname. Employee entity looks like this. @Entity @Table(name="emp") public class Employee implements Serializable {     private static final long serialVersionUID = 1L;     @Id     @GeneratedValue(strategy = GenerationType.AUTO)     private Long id;     @Column     private String firstname;     @Column     private String lastname;     @Column     private String username;     @Column     private String street;     @Column     private String city;     @Column     private String state;     @Column     private String zipc