You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 29, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 29, 2025. It is now read-only.
For a SQLite database of 45MB in size I need to wait around 60 seconds before being able to type a 2nd query inside the editor. In between each action this happens. I am running it on an Asus Zenbook 3, no performance issues in other applications whatsoever. On an i7 octacore desktop the same experience. Too much lag to be of any use.
Maybe the Atom editor is not suitable for these kind of things? The editor itself has been plagued with performance issues (have been using Atom from the start on occasions). They rewrote a couple of performance critical parts in C++, but it still isn't stellar.
RAM is max 500MB, what I noticed is that Falcon is using 47%+ CPU when not doing any queries or rendering. I am retrieving 26000 records for 2 columns. I noticed Falcon is starting to slow down after a doing a couple of queries (5+) and especially when switching queries between tables.
edit: 235 MB RAM after a fresh start and running the query
I'm going to label this issue as a bug. We had recently another issue report #257 where Falcon became very slow. Unfortunately, we don't know how to trigger this issue.
I'll try and see if I can reproduce it using a query retrieving so many records.
Activity
n-riesco commentedon Dec 11, 2017
Could you check how much RAM is Falcon using after the first request, please?
Also, how many rows and columns are you retrieving in this query?
titanomachy commentedon Dec 11, 2017
RAM is max 500MB, what I noticed is that Falcon is using 47%+ CPU when not doing any queries or rendering. I am retrieving 26000 records for 2 columns. I noticed Falcon is starting to slow down after a doing a couple of queries (5+) and especially when switching queries between tables.
edit: 235 MB RAM after a fresh start and running the query
n-riesco commentedon Dec 11, 2017
I'm going to label this issue as a bug. We had recently another issue report #257 where Falcon became very slow. Unfortunately, we don't know how to trigger this issue.
I'll try and see if I can reproduce it using a query retrieving so many records.