From fb9295d3e2580b06a37a1acaa756edb842247c54 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=C3=89der=20F=2E=20Zulian?= Date: Fri, 1 Apr 2016 17:46:38 +0200 Subject: [PATCH] Since SQLITE 3.7.x there are performance problems We used EXPLAIN QUERY PLAN and detected differences between machines. Matthias found out that faster machines (DRAM server) use the "ranges_index" for the "Transactions" table. But other machines (our laptops) use the primary key defined for that table. Removing the primary key the performance issues were solved. --- DRAMSys/simulator/resources/scripts/createTraceDB.sql | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/DRAMSys/simulator/resources/scripts/createTraceDB.sql b/DRAMSys/simulator/resources/scripts/createTraceDB.sql index e72ead68..aa236f83 100644 --- a/DRAMSys/simulator/resources/scripts/createTraceDB.sql +++ b/DRAMSys/simulator/resources/scripts/createTraceDB.sql @@ -48,8 +48,8 @@ CREATE VIRTUAL TABLE ranges USING rtree( ); CREATE TABLE Transactions( - ID INTEGER PRIMARY KEY, - Range INTEGER, + ID INTEGER, + Range INTEGER, Address INTEGER, Burstlength INTEGER, TThread INTEGER,