@@ -622,3 +622,163 @@ TIP 6: Have you searched our list archives?
622
622
623
623
http://www.postgresql.org/search.mpl
624
624
625
+ From pgsql-general-owner+M14602@postgresql.org Sat Sep 1 00:50:49 2001
626
+ Return-path: <pgsql-general-owner+M14602@postgresql.org>
627
+ Received: from server1.pgsql.org (server1.pgsql.org [64.39.15.238] (may be forged))
628
+ by candle.pha.pa.us (8.11.6/8.10.1) with ESMTP id f814onF24433
629
+ for <pgman@candle.pha.pa.us>; Sat, 1 Sep 2001 00:50:49 -0400 (EDT)
630
+ Received: from postgresql.org (webmail.postgresql.org [216.126.85.28])
631
+ by server1.pgsql.org (8.11.6/8.11.6) with ESMTP id f814pNq39726;
632
+ Fri, 31 Aug 2001 23:51:23 -0500 (CDT)
633
+ (envelope-from pgsql-general-owner+M14602@postgresql.org)
634
+ Received: from ns1.austin.rr.com (ns1.austin.rr.com [24.93.35.62])
635
+ by postgresql.org (8.11.3/8.11.4) with ESMTP id f81439f96700
636
+ for <pgsql-general@postgresql.org>; Sat, 1 Sep 2001 00:03:09 -0400 (EDT)
637
+ (envelope-from rsanford@nolimitsystems.com)
638
+ Received: from mightywombat (cs662523-179.houston.rr.com [66.25.23.179])
639
+ by ns1.austin.rr.com (8.12.0.Beta16/8.12.0.Beta16) with SMTP id f813x7pX027417
640
+ for <pgsql-general@postgresql.org>; Fri, 31 Aug 2001 22:59:07 -0500
641
+ From: "Robert J. Sanford, Jr." <rsanford@nolimitsystems.com>
642
+ To: <pgsql-general@postgresql.org>
643
+ Subject: Re: [GENERAL] PL/java?
644
+ Date: Fri, 31 Aug 2001 23:02:04 -0500
645
+ Message-ID: <HOEFIONAHHKFEFENBMNOAEPPCBAA.rsanford@nolimitsystems.com>
646
+ MIME-Version: 1.0
647
+ Content-Type: text/plain;
648
+ charset="US-ASCII"
649
+ Content-Transfer-Encoding: 7bit
650
+ X-Priority: 3 (Normal)
651
+ X-MSMail-Priority: Normal
652
+ X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
653
+ Importance: Normal
654
+ X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
655
+ In-Reply-To: <MAEFKNDLAHNIFMAIEGHJCEKJCDAA.knight@phunc.com>
656
+ Precedence: bulk
657
+ Sender: pgsql-general-owner@postgresql.org
658
+ Status: OR
659
+
660
+ note - i don't work for any of the companies whose products
661
+ are mentioned below. i have performed evaluations of these
662
+ products and the support provided when attempting to determine
663
+ what platform my company's systems should run on. unfortunately,
664
+ i did not choose orion and i am suffering for it now...
665
+
666
+ some goober blathered thusly:
667
+ > Have you ever actually used Java on an enterprise-level
668
+ > application? Ever see the Tomcat webserver? It uses
669
+ > 100MB of memory, drives the load on our server up to 8,
670
+ > and doesn't serve nearly as fast apache. Do you really
671
+ > want that in your database?
672
+
673
+ first - don't complain about java because you or someone
674
+ in your group/department/company made a poor decision on
675
+ what tools to use. that's like complaining about mexican
676
+ food when the only experience you have is eating an out-
677
+ dated frozen burrito from the 7-11 freezer.
678
+
679
+ when looking at the performance of java you have to take
680
+ a look at two things - first you have to compare various
681
+ java implementations against each other and then you have
682
+ to compare the best java implementations against native
683
+ c/c++ code. the following link does that. the java tests
684
+ include tomcat, orion, websphere, and resin. jrun and
685
+ weblogic were originally included in the testing but
686
+ were both removed at their companies' request.
687
+
688
+ the tests also compare orion vs microsoft asp running on
689
+ win2k and iis5. all tests run on the same hardware.
690
+
691
+ what i believe these tests clearly demonstrate is that
692
+ java is not the problem, the implementation applications
693
+ based on java is. i also do not believe that tomcat is
694
+ a fair representation of java performance in that it is
695
+ intended to be a reference implementation. as such, the
696
+ code base should sacrifice performance for clarity.
697
+
698
+ http://www.orionserver.com/benchmarks/benchmark.html
699
+
700
+
701
+ while not in the benchmark i would also like to
702
+ recommend jetty as an app server. it is an opensource,
703
+ 100% java web and application server. in its base form
704
+ it is "just" a web, servlet, and jsp engine. it does,
705
+ however, have contributed code providing integration
706
+ with other j2ee opensource projects such as the JBoss
707
+ EJB engine.
708
+
709
+ you can find the jetty home page at:
710
+ http://jetty.mortbay.com/
711
+
712
+ and then they blathered some more:
713
+ > Compare the speed of Oracle 8 with 8i if you don't
714
+ > believe me. The stability is also much worse. Ever
715
+ > see a JVM on any platform that didn't crash if you
716
+ > looked at it cockeyed? Ever really trust the garbage
717
+ > collection? I don't. I've found a memory leak in IBM
718
+ > developed java libraries. Gotta restart that app
719
+ > every once in a while to reclaim system resources it
720
+ > gobbled up and never gave back.
721
+
722
+ some mention was made regarding the performance of
723
+ the oracle8i application server. well, oracle has
724
+ realized that their performance was sub-optimal and
725
+ rectified the situation by licensing the orion server
726
+ for oracle9i. while money and politics most certainly
727
+ play a part in any licensing arrangement they must
728
+ also realize that making customers happy through the
729
+ performance of their applications will lead to more
730
+ money. the link to the press release is below.
731
+
732
+ http://www.oracle.com/corporate/press/index.html?759347.html
733
+
734
+ all of that being said...
735
+
736
+ i don't think that the person that started this thread
737
+ did anything wrong by making the request they did. that
738
+ is what opensource is all about - contributions, even
739
+ just contributions of ideas, are welcomed. even so, there
740
+ are several options that i see for getting it implemented:
741
+ 1) its an open source project so implement it yourself.
742
+ while i have never worked on modifying the code base
743
+ i am extremely confident that the current developers
744
+ will be more than willing to give you advice and
745
+ pointers.
746
+ 2) if #1 is not feasible either because you don't have
747
+ the time, the inclination, or the experience then
748
+ you can write a contract that will pay one of the
749
+ postgres developers to implement it for you.
750
+ 3) if that isn't feasible you can try to get a volunteer
751
+ to do so.
752
+ 4) if that isn't feasible then you either have to live
753
+ with what you have, go elsewhere, or be quiet.
754
+
755
+ to the person that blathered thusly in response to the
756
+ request for java:
757
+ > Merits of the language notwithstanding, I'd rather
758
+ > not have a buggy, still under development
759
+ > (depreciating everything under the sun with every
760
+ > new iteration) JVM parasite in my DB.
761
+
762
+ informed and intelligent debate is good. given that i
763
+ believe such to be true, i would request that you
764
+ refrain from blathering such vitriol and uninformed
765
+ nonsense. not only is it for the good of the people
766
+ on the list who don't want to hear it but it will
767
+ also do you good by not telling everyone out there
768
+ that you are a very silly person that doesn't deal
769
+ with logic and/or facts.
770
+
771
+ to everyone else on the list - if we all contribute
772
+ a penny we could probably buy enough burritos from
773
+ 7-11 to make sure that his hands and mouth are busy
774
+ for a good long while.
775
+
776
+ rjsjr
777
+
778
+
779
+
780
+ ---------------------------(end of broadcast)---------------------------
781
+ TIP 3: if posting/reading through Usenet, please send an appropriate
782
+ subscribe-nomail command to majordomo@postgresql.org so that your
783
+ message can get through to the mailing list cleanly
784
+
0 commit comments