On Wed, Jun 5, 2019 at 5:31 PM Joe Murphy <joseph.b.murp...@gmail.com>
wrote:

>
> https://blog.idrsolutions.com/2015/03/why-we-are-abandoning-imageio-and-jai-for-image-support-in-our-commercial-java-code/
>

We took a similar road several years ago when imageio-ext and jai-ext have
been created.

There is really no reason to use imageio native bindings left, GeoServer
has faster PNG
encoding embedded since years (thanks to the PNGJ library) and faster JPEG
encoding/decoding
tanks to the turbo-jpeg pluging. The TIFF reader has been replaced and the
image streams too.

When it comes to jai-ext, which are the image processing operations like
scaling/reprojecting,
the direction has been fixes, ROI support everywhere, and NODATA support.
Performance was still considered, but operations are generally not as fast
as the native JAI equivalents
(they are normally as fast as the pure java JAI or faster, but providing
improved correctness and features,
and when you really start using the extra features, there's a performance
penalty as there is more work involved).

It's up to you to decide where you want to go. If you want highest possible
performance and you don't need
NODATA support, you have no masks, you reproject data very seldomly or see
no white/black lines in the output,
then disable jai-ext and stick to Java 8 + native JAI. Mind this is a path
that is going to eventually die out,
getting native JAI builds is harder and GeoServer tests are no longer
checking proper functionality
under those conditions (since 2.15.0 was released). But it should be viable
for a little while longer.

I'd suggest to run a benchmark comparing the two options, and see if you
can live with the better supported version
(jai-ext) or actually need to go and use native JAI to get the required
performance for your use case

Cheers
Andrea

GeoServer Professional Services from the experts! Visit http://goo.gl/it488V
for more information. == Ing. Andrea Aime @geowolf Technical Lead
GeoSolutions S.A.S. Via di Montramito 3/A 55054 Massarosa (LU) phone: +39
0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549
http://www.geo-solutions.it http://twitter.com/geosolutions_it
------------------------------------------------------- *Con riferimento
alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 -
Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni
circostanza inerente alla presente email (il suo contenuto, gli eventuali
allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i
destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per
errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le
sarei comunque grato se potesse darmene notizia. This email is intended
only for the person or entity to which it is addressed and may contain
information that is privileged, confidential or otherwise protected from
disclosure. We remind that - as provided by European Regulation 2016/679
“GDPR” - copying, dissemination or use of this e-mail or the information
herein by anyone other than the intended recipient is prohibited. If you
have received this email by mistake, please notify us immediately by
telephone or e-mail.*
_______________________________________________
Geoserver-users mailing list

Please make sure you read the following two resources before posting to this 
list:
- Earning your support instead of buying it, but Ian Turton: 
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines: 
http://geoserver.org/comm/userlist-guidelines.html

If you want to request a feature or an improvement, also see this: 
https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer


Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to