On 05/27/2013 11:43 AM, Ladislav Slezak wrote:
Originally I wanted to put the results directly here, but a spreadsheet
document looks better, it's available here:
https://docs.google.com/spreadsheet/ccc?key=0ArPH-PKhmo3kdFRFUy05WG50ckpCVHJpVXFJRGYwd2c&usp=sharing
Very nice and complete data. Thanks!
I've cloned the document and added some graphs just to give the data a
graphical representation:
https://docs.google.com/spreadsheet/ccc?key=0AhWDup9rfv8cdE83WmlrelpwVzhGX0phVnZiRE91clE#gid=0
Possible improvements:
-----------------------
Currently we include _complete_ ruby in inst-sys, including parts which
are not
needed for the installer (like webrick web server, test unit, rdoc, rake,
xmlrpc, ....). It's possible to remove these parts and save some space in
inst-sys which is stored in RAM. It's possible to include just a part of
an RPM
package to inst-sys instead of complete package.
Also the added fast_gettext gem could be filtered to save few kilobytes...
It's great to have a plan. I believe this can wait till the code is good
enough to be switched to Ruby in master. Then we can do some optimizations.
Later we could also do some cleanup and use native Ruby library instead
of our
implementation (e.g. use native net/ftp.rb instead of our FTP.ycp
(converted to
FTP.rb), the same applies to String.ycp, URL.ycp...)
Additionally, it seems that the YCP code currently caches some data that
are not needed anymore. And the Ruby implementation does the same: it
copies the data instead of sharing them - which is expected as it's been
planned to behave the same way as YCP after the conversion. I see a big
potential for minimizing the memory usage after some data-handling
related refactoring in converted YaST.
Thanks and Bye
Lukas
--
Lukas Ocilka, Cloud & Systems Management Department
SUSE LINUX s.r.o., Praha
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
