From: Xan <dxpublica@telefonica.net>
To: Mojca Miklavec <mojca.miklavec.lists@gmail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: texexec with 2 processors?
Date: Fri, 28 Aug 2009 10:26:58 +0200 [thread overview]
Message-ID: <4A9794D2.3020306@telefonica.net> (raw)
In-Reply-To: <6faad9f00908272315x204e39a3v8b4482e61809ffb5@mail.gmail.com>
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 other applications
> continue to run smoothly instead of being blocked by TeX using 95% of
> both processors.)
>
I did not say to process page 500 before the page 499. I just say use
all power of the multiple processors.
>
>> It could be useful for offering typesetting services. I'm thinking about
>> having a computation service like alpha.wolfram but with ConTeXt. Like
>> ConTeXt online but benefit from multiple processors....
>>
>
> If you would offer a service, you would get multiple requests at the
> same time anyway, so there's no real need for that in this case
> (you'll face many more serious problems when offering typesetting
> service).
>
>
You are right here.
>> Joking, perhaps you could fix it in Mark VII ;-)
>>
>
> You can try XeTeX if you want to put load on both processors. It does
> offer a parallel process as far as I heard,
Is it true?
> but then you'll probably
> want support for quad-core once you get a better computer :)
>
> Mojca
>
Xan.
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-08-28 8:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 19:40 Xan
2009-08-27 20:22 ` Taco Hoekwater
2009-08-27 22:34 ` Xan
2009-08-28 6:14 ` Mojca Miklavec
2009-08-28 6:34 ` luigi scarso
2009-08-28 7:15 ` Taco Hoekwater
2009-08-28 7:57 ` luigi scarso
[not found] ` <6faad9f00908272315x204e39a3v8b4482e61809ffb5@mail.gmail.com>
2009-08-28 8:26 ` Xan [this message]
2009-08-28 9:50 ` Mojca Miklavec
2009-08-28 10:07 ` Xan
2009-08-28 11:03 ` Hans Hagen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A9794D2.3020306@telefonica.net \
--to=dxpublica@telefonica.net \
--cc=mojca.miklavec.lists@gmail.com \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).