[xep-support] Re: Java 8 Update

We just tested VDPMill with the same document on the same machine. VDPMill
can split and merge back together at a configurable package size. The
individual "chunks" of documents can be run simultaneously in threads of
rendering, joining together results into a single output PDF.

Java 7: 91.24 pages/second
Java 8: 124.23 pages/second

This was running VDPMill connected to XEP through Java API as the rendering
engine. VDPMill can be placed on top of EnMasse to spread the load further
on that machine or even on multiple machines using TCP communication from
VDPMill to underlying threads of RenderX XEP. In the current configuration
with only a single XEP local, the CPU reached about 33% utilization. Based
on past performance, this mean that this would approach 160-180 pages/second
under EnMasse on this machine with VDPMill.

Again, a smaller but noticeable performance boost when switching to Java 8
over Java 7.
Java 7 from Java 6 saw about the same boost in performance.

Kevin Brown
(650) 327-1000 Direct
(650) 328-8008 Fax
(925) 395-1772 Mobile
skype:kbrown01
kevin@renderx.com
sales@renderx.com
http://www.renderx.com

-----Original Message-----
From: Xep-support [mailto:xep-support-bounces@renderx.com] On Behalf Of
Kevin Brown
Sent: Wednesday, November 12, 2014 12:24 PM
To: 'RenderX Community Support List'
Subject: [xep-support] Java 8 Update

Just a note for all on the list.
We conducted some unofficial testing today. We will do more prior to next
release.
A quad-core laptop running RenderX XEPWin with both Java 7 64-bit and Java 8
64-bit installed.
Processing a single document of 2800 pages XML+XSL to FO to PDF.
The document was invoices approximately 4 to 5 pages each with two custom
SVG charts (created via XSL) in each document so 1200+ custom, unique
charts.
The document also includes tabular data. The XML was run simply via XEP
Assistant, just selecting the large XML with XSL stylesheet and processing
to PDF format as a single document (meaning not using VDPMill to split and
merge).

Java 7: 32.56 pages/second
Java 8: 42.42 pages/second

A significant performance boost.

We encountered no issues at all with Java 8.

The RenderX XEPWin installer at this time would not recognize Java 8 so in
order to configure it at this time, you can edit the
Cliserservice.exe.config to point to a Java 8 installation and restart the
service.

At this time, we feel confident to say Java 8 is supported.

Kevin Brown
RenderX

_______________________________________________
(*) To unsubscribe, please visit
http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service
http://w ww.renderx.com/terms-of-service.html

_______________________________________________
(*) To unsubscribe, please visit http://lists.renderx.com/mailman/options/xep-support
(*) By using the Service, you expressly agree to these Terms of Service http://w
ww.renderx.com/terms-of-service.html
Received on Wed Nov 12 13:13:27 2014