2011/8/31 Александр Москалёв <ir...@irker.net>

> Hello!
>

Hi Irker ;)


>
> Yannick, this mail is primarily for you, but I decided that I can
> discuss it with everyone.
>
> As I already told you, I will try to join the development edit.php.net.
>
> The first thing I want to optimize the updating cron script.
> Now when you run it removes all data from the database and all files
> are verified.
> I suggest to parse the output of svn update (we can use the option
> "svn - xml"). From this result we can figure out which specific files
> to delete or recheck (including lang files if en file modified or
> deleted).
> Because recheck process is long, and we must not lose information
> about changed files, we must to separate this function in other cron:
> "update script" check svn update, delete deleted files from database
> and mark files to recheck in DB.
> "recheck script" find some portion of files in DB and rechecking it,
> mark as rechecked. This portion will recheck in one transaction. Then
> recheck next portion...
> also while this rechecking some files marked as "not in en".
> In case when "update script" was crashed or make error we will be
> needed to recheck all files as in current cron script.
>
> I think this modification can do update process more faster.
> What all you think about it and can someone help me with this work,
> becouse I have little free time for this?
>
>
Why not ! But I just don't see why this is a problem that this processus
take some minutes (2 minutes ?).
There is a lot of work that can be done on the editor (like track bugs
repported this lasts weeks), cleaning the code (Js and/or Php), etc.
But I really don't see why you want to do this optimisation ;)

Anyways, if you want to do it, do it ;) But I just don't want that this
processus became to hard to understand. Actually, it's "simple" and I just
want to stay it "simple" ;)

Best,
Yannick


>
>
> P.S.: after discussion I can create branch for this. sorry for my English!
>
>
> With regards, Alexander Moskaliov
> ir...@irker.net
>

Reply via email to