Re: [Evolution] Places where Evolution stores its data



Am Freitag, den 29.05.2015, 00:10 +0100 schrieb Patrick O'Callaghan: 
On Thu, 2015-05-28 at 20:25 +0200, Tom wrote:
What is your opinion on that ?

My opinion is that:

1) You haven't said what version of Evo this is, but if it's the one
you used to post your message it's several years out of date.

2) Your directory listing gives no idea of how much space all this
takes up, so it's impossible to say if it's a problem.

drwx------  4 thomas thomas 4,0K Jun 14 14:55 1420542095 9361 4 ga-78/
drwx------  3 thomas thomas 1,3M Jun 14 16:49 1420635858 9770 2 ga-78/
drwx------  4 thomas thomas 4,0K Jun 14 15:26 1425977221 3489 2 ga-78/

The disk space sure isn't a problem, but the behaviour of Evolution when
being closed. It seems that the attached database walks through all
these listed newsgroups and does something like (for each of them):
===========
DB SQL operation [SELECT COUNT (*) FROM 'za.unix.misc' where read=0 or
read=1] started
Camel SQL Exec:
SELECT COUNT (*) FROM 'za.unix.misc' where read=0 or read=1
DB Operation ended. Time Taken : 0,000169
###########

===========
DB SQL operation [SELECT COUNT (*) FROM 'za.unix.misc' WHERE junk = 1]
started
Camel SQL Exec:
SELECT COUNT (*) FROM 'za.unix.misc' WHERE junk = 1
DB Operation ended. Time Taken : 0,000050
###########

===========
DB SQL operation [SELECT COUNT (*) FROM 'za.unix.misc' WHERE deleted =
1] started
Camel SQL Exec:
SELECT COUNT (*) FROM 'za.unix.misc' WHERE deleted = 1
DB Operation ended. Time Taken : 0,000044
###########

===========
DB SQL operation [SELECT COUNT (*) FROM 'za.unix.misc' WHERE read = 0]
started
Camel SQL Exec:
SELECT COUNT (*) FROM 'za.unix.misc' WHERE read = 0
DB Operation ended. Time Taken : 0,000041
###########

===========
DB SQL operation [SELECT COUNT (*) FROM 'za.unix.misc' WHERE junk = 0
AND deleted = 0] started
Camel SQL Exec:
SELECT COUNT (*) FROM 'za.unix.misc' WHERE junk = 0 AND deleted = 0
DB Operation ended. Time Taken : 0,000048
###########

===========
DB SQL operation [SELECT COUNT (*) FROM 'za.unix.misc' WHERE junk = 1
AND deleted = 0] started
Camel SQL Exec:
SELECT COUNT (*) FROM 'za.unix.misc' WHERE junk = 1 AND deleted = 0
DB Operation ended. Time Taken : 0,000047
###########

===========
DB SQL operation [BEGIN] started
Camel SQL Exec:
BEGIN
Camel SQL Exec:
DELETE FROM folders WHERE folder_name = 'za.unix.misc'
Camel SQL Exec:
INSERT INTO folders VALUES ( 'za.unix.misc', 14, 0, 0, 0, 0, 0, 0, 0, 0,
0, '1 0 0' ) 
Camel SQL Exec:
COMMIT

If this was done for the 5 or 6 groups I'm subscribed to, I couldn't
care less. But seeing it to be done for app. 23000 entries lasts app. 3
hours. So we had to instruct all users to --force-shutdown - but that
can't be the professional solution ... 

3) Evo generally has a directory for each account, but some of these
look older than others. Perhaps some accounts were closed and
re-opened, or restored from a backup, or imported from a different
machine.

For the emae* I'd like to follow Milan and consider them of no
importance but as I just read here, I list them again and see they were
all touched June,2 ???
those keep mail>>>>>>>>>
drwx------  4 thomas thomas 4,0K Jun 14 10:35 1426853623 16921 2 ga-78/
drwx------  2 thomas thomas 4,0K Jun  2 18:39
emae-check-authtype-0x10127ae0/
of those kind are older >>>



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]