Hell yeah :D
RESTORING imdbIDs values for movies... DONE! (restored 2102978 entries out of
2104144)
# TIME restore movies : 0min, 47sec (wall) 0min, 0sec (user) 0min, 0sec (system)
RESTORING imdbIDs values for people... DONE! (restored 3544106 entries out of
3545620)
# TIME restore people :
On Sun, Feb 12, 2012 at 14:20, Emmanuel Tabard m...@webitup.fr wrote:
Fair enough !
When it was selecting all the not null ids, the memory of the process grows
up and the size of the .db never grows up.
My theory is that dbm save on close ? Does that make sense ?
Strange (even if, being
I was wondering, why don't you use the original dbs ?
Something like that takes 3 seconds:
CREATE TABLE title_extract SELECT imdb_id, md5sum FROM title WHERE imdb_id IS
NOT NULL
CREATE TABLE name_extract SELECT imdb_id, md5sum FROM name WHERE imdb_id IS NOT
NULL
And use your query to
Here is a little workarround :
-- Extract imdb_id and md5sum (6sec)
CREATE TABLE title_extract SELECT imdb_id, md5sum FROM title WHERE imdb_id IS
NOT NULL;
CREATE TABLE name_extract SELECT imdb_id, md5sum FROM name WHERE imdb_id IS NOT
NULL;
-- Add indexes (12sec)
ALTER TABLE title_extract
On Sun, Feb 12, 2012 at 16:50, Emmanuel Tabard m...@webitup.fr wrote:
Here is a little workarround :
Well, that's a very interesting solution, thanks. :-)
Anyway, I have to think a little about it: storing the data in the
filesystem granted
us the possibility to split the CSV mode into 2
Well, that's a very interesting solution, thanks. :-)
I made a test run with this solution.
Time to save/restore : 6minutes
Restoring success :
- People : 99.8777%
- Movies : 99.8845%
Anyway, I have to think a little about it: storing the data in the
filesystem granted
us the
On Tue, Feb 7, 2012 at 09:20, Davide Alberani davide.alber...@gmail.com wrote:
As usual, I'm really busy right now... I hope to have time to give it
a look this weekend.
Ehi, snowstorms buy you a lot of free time... :-P
It was easier that I thought, mostly thanks to the fact the we already
On Sat, Feb 11, 2012 at 22:06, Emmanuel Tabard m...@webitup.fr wrote:
Looks nice !!!
Well, it's not exactly nice clean code... let's hope it works.
It seems that you load all the datas in memory before storing it in the temp
databases.
cls.select(ISNOTNULL(cls.q.imdbID))
Maybe you should
On Mon, Feb 6, 2012 at 09:10, Emmanuel Tabard m...@webitup.fr wrote:
Feb 6 07:16:53 ks380342 kernel: Out of memory: Kill process 29782
(imdbpy2sql.py) score 718 or sacrifice child
Feb 6 07:16:53 ks380342 kernel: Killed process 29782 (imdbpy2sql.py)
total-vm:18212980kB,
Feb 6 07:16:53 ks380342 kernel: Out of memory: Kill process 29782
(imdbpy2sql.py) score 718 or sacrifice child
Feb 6 07:16:53 ks380342 kernel: Killed process 29782 (imdbpy2sql.py)
total-vm:18212980kB, anon-rss:18149024kB, file-rss:64kB
Greedy boy :D
Le 27 janv. 2012 à 09:18, Davide
Could you provide the methods you use for update and initial db creation,
or pastebin the code.
On Thu, Jan 26, 2012 at 9:32 AM, Emmanuel Tabard m...@webitup.fr wrote:
hi,
First of all, thank you for imdbpy. This is really plug'n play, well done
!!!
Context :
- Import all imdb database
On Thu, Jan 26, 2012 at 15:32, Emmanuel Tabard m...@webitup.fr wrote:
First of all, thank you for imdbpy. This is really plug'n play, well done !!!
Thanks. :-P
Context :
- Import all imdb database (from text dumps) - first time it's fast and ok
- I have the imdb ids for 90% of titles and
12 matches
Mail list logo
