Le 05/07/2012 18:56, Luke Kanies a écrit :
I agree that parallelization might make a big difference, but it has the chance
to be a world of hurt, too. Threading in general is hard, threading in ruby is
ridiculous, and threading around operations on the system whose interactions
you can't predict (e.g., two package updates at a time, or a package update and
a user change) might be completely insane.
It is sure that we cannot "just parallelized" everything and it's works. I think there is 2 things : adding threading
with tread-safety, and taking care that things that run in parallel are compatible.
File objects could be parallelized without too much ricks by example, as long
as graph dependencies are respected.
However, I think there's a lot of room for improvement that gets us close to
but not quite at parallel operation, such as grouping package operations (which
could be done now, albeit not trivially), and having better hooks in the RAL
for when a resource is ready for operation, so there's less blocking.
This is ticket #2198 :)
Aurélien
--
You received this message because you are subscribed to the Google Groups "Puppet
Developers" group.
To post to this group, send email to puppet-dev@googlegroups.com.
To unsubscribe from this group, send email to
puppet-dev+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-dev?hl=en.
