[Qt-interest] Multiple page rendering using webkit

[Jason H]

It depends how large 'large' is. I think I/O delay would dominate. And 4.7's 
QNAM (QNetworkAccessManager) is single threaded. 4.8 will (supposedly) have a 
multi-threaded QNAM, so you're looking at paint time in the main thread. 

1 sounds fine
2 sounds fine, but you'll have to coordinate the multiple processes. How woudl 
you handle interactivity?



You could put the QNAM in another thread for 1, and get a solution in the 
middle.



________________________________
From: Tarandeep Singh <tarandeep at gmail.com>
To: qt-interest <qt-interest at trolltech.com>
Cc: webkit-qt at lists.webkit.org
Sent: Fri, April 15, 2011 3:33:07 PM
Subject: [Qt-interest] Multiple page rendering using webkit

Hi,

I need to render a large number of pages and obviously need do this as 
efficiently as possible.
Since GUI rendering needs to be done on the main thread, so I can't create 
multiple QWebPage threads.

So I am thinking of these 2 solutions-

1) Create one process and have N QWebPage instances so that N pages can be 
rendered simultaneously. Here assumption is QT+Webkit behind the scenes create 
threads to do parallel IO etc.

2) Create N processes where each process handles 1 page request at a given time.

Can someone please advice which solution should work better or is there is 
another way to achieve this.
I have 16 cores and 32G of RAM.

Thanks!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20110415/d6482a0e/attachment.html