On Fri, Aug 28, 2009 at 00:34, Xan wrote:
En/na Taco Hoekwater ha escrit:
Xan wrote:
Hi,
I have Intel Core Duo and when I run texexec the CPU resource in gnome is
marked about 50%. Is it mean that texexec only use one processor? If it's,
can you think to improve it for scalability?
Just
You cannot start processing page 500 before you know where page 499
wil end. TeX is not really a kind of application where you would gain
a lot by parallelization. And honestly, I don't remember seing many
applications using both cores. (Plus: I'm happy if other applications
continue to run
luigi scarso wrote:
You cannot start processing page 500 before you know where page 499
wil end. []
Hm, not so sure. Think for example to a book with 3 chapters, and you
know at priori that there are not relations
The root of the problem is that because TeX is a programming language
as
On Fri, Aug 28, 2009 at 9:15 AM, Taco Hoekwatert...@elvenkind.com wrote:
luigi scarso wrote:
You cannot start processing page 500 before you know where page 499
wil end. []
Hm, not so sure. Think for example to a book with 3 chapters, and you
know at priori that there are not relations
En/na Mojca Miklavec ha escrit:
You cannot start processing page 500 before you know where page 499
wil end. TeX is not really a kind of application where you would gain
a lot by parallelization. And honestly, I don't remember seing many
applications using both cores. (Plus: I'm happy if
On Fri, Aug 28, 2009 at 10:26, Xan wrote:
En/na Mojca Miklavec ha escrit:
You cannot start processing page 500 before you know where page 499
wil end. TeX is not really a kind of application where you would gain
a lot by parallelization. And honestly, I don't remember seing many
En/na Mojca Miklavec ha escrit:
Well, yes. But you need to delegate a time consuming task A to
processor 1 and another time consuming task B to processor 2 where
both tasks need to be independent from each other and then you may
join the results at the end, else you spend more resources for
Mojca Miklavec wrote:
As Taco confirmed, it seem to run xetex and xdipdfmx in separate processes.
another example is running luatex in a virtual machine using one cpu in
which case some file/disk io is done by an other (due the layered disk
handling)
Hans
Hi,
I have Intel Core Duo and when I run texexec the CPU resource in gnome
is marked about 50%. Is it mean that texexec only use one processor? If
it's, can you think to improve it for scalability?
Just a curious question.
Xan.
PS: Please, CCme.
Xan wrote:
Hi,
I have Intel Core Duo and when I run texexec the CPU resource in gnome
is marked about 50%. Is it mean that texexec only use one processor? If
it's, can you think to improve it for scalability?
Just a curious question.
Run two jobs at once ;-)
Seriously: no, typesetting
En/na Taco Hoekwater ha escrit:
Xan wrote:
Hi,
I have Intel Core Duo and when I run texexec the CPU resource in
gnome is marked about 50%. Is it mean that texexec only use one
processor? If it's, can you think to improve it for scalability?
Just a curious question.
Run two jobs at once
11 matches
Mail list logo
