Hi Simon,
Here is my proposal to solve this long standing bug:
Didn't pushed on Alioth, as I'm not sur you'd liek it.
https://github.com/a-detiste/game-data-packager/commit/e18cf07dc514b8e450033223346f35c7642795d9
Greets,
Alexandre
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.
2015-03-13 1:09 GMT+01:00 Simon McVittie :
> Next idea: YAML is pretty complicated, JSON is much simpler while still
> human-editable, maybe we can use that? That turns out to be simple to
> do, and is another factor of 20 speedup. I'll push the results shortly.
This also seems much less intrusive
On 09/03/15 19:25, Alexandre Detiste wrote:
[smcv wrote:]
>> Perhaps if we profiled what takes all the time, we'd be able to avoid it
>> - e.g. by "compiling" the parts of the YAML files that are actually
>> needed for the argument parser into a pickle file or something, and
>> loading the rest laz
Hi,
> To be fair, judging by your shell prompt
And that's the new souped-up version (see uname's 4 cores output),
on the old one a plain "./run" almost nears two minutes
while GDP v37 ran in 0.2 seconds.
On an Amd Duron from 2005 that is still perfect for most
GDP games & Youtube; I get 10 secon
On 06/03/15 15:13, Alexandre Detiste wrote:
> Running GDP without any argument also takes a very long time;
> users may think it has hanged.
>
> pi@raspberrypi ~/game-data-packager $
To be fair, judging by your shell prompt, you're running it on the I/O
coprocessor of a slightly outdated video de
Package: game-data-packager
Version: 39
Severity: minor
Dear Maintainer,
When a user ask GDP to package some game,
GDP will read _all_ yaml files.
As the number of supported games rises,
it gets worse.
Running GDP without any argument also takes a very long time;
users may think it has hanged.
6 matches
Mail list logo
