--
You received this message because you are subscribed to the ADF Enterprise Methodology Group (http://groups.google.com/group/adf-methodology). To unsubscribe send email to adf-methodolo...@googlegroups.com
All content to the ADF EMG lies under the Creative Commons Attribution 3.0 Unported License (http://creativecommons.org/licenses/by/3.0/). Any content sourced must be attributed back to the ADF EMG with a link to the Google Group (http://groups.google.com/group/adf-methodology).
Well, to be honest.
If you want that many concurrent users, don't go for ADF
ADF is centered on easy of development and reducing the required
knowledge to build enterprise applications.
Performance will never be as good as other JEE framework.
ADF can execute several more queries than required for a lot of
operations.
I have had several SR request with Oracle concerning duplicate or even
triple query firing of queries.
ADF has sacrificed a lot in order to fully support drag and drop and
generic components.
Just create a simple application and start using it. See the memory
usage and CPU goes insane for a single user.
In my opinion Weblogic is the best JEE application server, but it is a
heavy weight server supporting a lot of features.
Features of which ADF uses almost nothing, features intended for JEE
frameworks.
The concurrent users you descibe I have had to deal with in only 1
project.
ADF was never an option there, we quickly moved to EJB 3.0 with a thin
Java layer and WFD (Microsoft) gui in order to support the load.
JEE can scale horizontal and vertical. ADF will not, simple due to the
application module being so heavy and the concept of a statefull
session facade.
If you check other JEE frameworks you see they quickly moved away from
state full session facades, EJB state full beans etc. ADF has not.
This type of programming paradigm just doesn't allow for scalability
under high concurrent.
users. Yet ADF keeps its application module, which is even heavier
then any other state full session facade out there.
ADF works, but the use in my opinion is limited.
ADF works in back end data entry application working mainly directly
on database tables.
It reduces the complexity of JEE application but imposes certain
drawbacks, one of them being performance and scalability.
And yes, I use ADF, but for exactly the type of application I
mentioned above, Back end application working 85% directly on tables,
10% with PL/SQL procedures and 5% with rest/soap services.
-Anton
On Dec 18, 3:02 pm, amir hosein khanof <amir.kha...@gmail.com> wrote:
> Hi Sempon,
>
> Thanks for your sympathy, I completely came up with your idea regarding ADF
> but my problem is that when we say ADF is for Enterprise level
> applications it is antithesis, during the past 3 years of improving of ADF
> from Oracle, what I see is that in every version we see new feature and
> lack of improvement in performance issue. blieve me that even the AM
> Pooling in high load is not as good as must be.
> in OOW I heard that Oracle is going to use ADF for all the
> future applications that is going to be develope in Oracle, I wonder how it
> could be with this performance!!!
>
> Even the built-in application that Oracle himself has wrote that is not
> good in performance i.e take a look over Oracle Workspace or Oracle
> Worklist!!! when you try to login in, you feel that you are loading
> 1,000,000 records from db!!!
>
> what is the future? in case of Oracle Technologies which technology we must
> really use for Enterprise Level?
>
> When Oracle talks about Cloud how it could be possible with lack of
> performance?
>
> I really advocate ADF but the future is vague for me...
>
> Thanks,
>
> On Sun, Dec 18, 2011 at 3:19 PM, Simon Lessard <simon.lessar...@gmail.com>wrote:
>
>
>
>
>
>
>
>
>
> > Hi Amir,
>
> > If you already code applications using only 3Gb for 150 concurrent users,
> > which is 20Mb per user, then you're already doing pretty good and I don't
> > think I can come up with many potential optimizations. You could use full
> > client state saving (not token), but there are some potential security
> > risks associated with that and it's going to increase the network load.
> > Dropping the ADF Databinding layer and using POJOs as return values from
> > your application module methods can also yield some interesting RAM gains.
> > Other than that there isn't much really as JSF is a bit memory hungry by
> > design because of the said state saving.
>
> > I don't think Facebook could have been coded in ADF, it just not the right
> > framework model for that kind of application, it's really more intranet
> > oriented imho. I did work on some general public applications that ended up
> > pretty well, we still had to twist the framework around every corners to
> > resolve that kind of issues.
>
> > Regards,
>
> > ~ Simon
>
> > On Sun, Dec 18, 2011 at 11:30 AM, amir hosein khanof <
> > *CMA** **CGM SYSTeMS
> > **4, quai d’Arenc, 13235 Marseille cedex 02, France*
> > *( +33 6 79 37 39 85 (France)*
> > *(** **+**1.418.930.0279 (Canada)*
>
> > --
> > You received this message because you are subscribed to the ADF Enterprise
> > Methodology Group (http://groups.google.com/group/adf-methodology). To
> > unsubscribe send email to adf-methodolo...@googlegroups.com
>
> > All content to the ADF EMG lies under the Creative Commons Attribution 3.0
> > Unported License (http://creativecommons.org/licenses/by/3.0/). Any
> > content sourced must be attributed back to the ADF EMG with a link to the
> > Google Group (http://groups.google.com/group/adf-methodology).
>
> --
> Amir Khanof
> Senior Oracle MiddleWare Developer
>
> 09122124673
--
You received this message because you are subscribed to the ADF Enterprise Methodology Group (http://groups.google.com/group/adf-methodology). To unsubscribe send email to adf-methodolo...@googlegroups.com
All content to the ADF EMG lies under the Creative Commons Attribution 3.0 Unported License (http://creativecommons.org/licenses/by/3.0/). Any content sourced must be attributed back to the ADF EMG with a link to the Google Group (http://groups.google.com/group/adf-methodology).
> Hi Sempon,
>
> Thanks for your sympathy, I completely came up with your idea regarding ADF
> but my problem is that when we say ADF is for Enterprise level
> applications it is antithesis, during the past 3 years of improving of ADF
> from Oracle, what I see is that in every version we see new feature and
> lack of improvement in performance issue. blieve me that even the AM
> Pooling in high load is not as good as must be.
> in OOW I heard that Oracle is going to use ADF for all the
> future applications that is going to be develope in Oracle, I wonder how it
> could be with this performance!!!
>
> Even the built-in application that Oracle himself has wrote that is not
> good in performance i.e take a look over Oracle Workspace or Oracle
> Worklist!!! when you try to login in, you feel that you are loading
> 1,000,000 records from db!!!
>
> what is the future? in case of Oracle Technologies which technology we must
> really use for Enterprise Level?
>
> When Oracle talks about Cloud how it could be possible with lack of
> performance?
>
> I really advocate ADF but the future is vague for me...
>
> Thanks,
>
> On Sun, Dec 18, 2011 at 3:19 PM, Simon Lessard <simon.lessar...@gmail.com>wrote:
>
>
>
>
>
>
>
>
>
> > Hi Amir,
>
> > If you already code applications using only 3Gb for 150 concurrent users,
> > which is 20Mb per user, then you're already doing pretty good and I don't
> > think I can come up with many potential optimizations. You could use full
> > client state saving (not token), but there are some potential security
> > risks associated with that and it's going to increase the network load.
> > Dropping the ADF Databinding layer and using POJOs as return values from
> > your application module methods can also yield some interesting RAM gains.
> > Other than that there isn't much really as JSF is a bit memory hungry by
> > design because of the said state saving.
>
> > I don't think Facebook could have been coded in ADF, it just not the right
> > framework model for that kind of application, it's really more intranet
> > oriented imho. I did work on some general public applications that ended up
> > pretty well, we still had to twist the framework around every corners to
> > resolve that kind of issues.
>
> > Regards,
>
> > ~ Simon
>
> > On Sun, Dec 18, 2011 at 11:30 AM, amir hosein khanof <
> > *CMA** **CGM SYSTeMS
> > **4, quai d’Arenc, 13235 Marseille cedex 02, France*
> > *( +33 6 79 37 39 85 (France)*
> > *(** **+**1.418.930.0279 (Canada)*
>
> > --
> > You received this message because you are subscribed to the ADF Enterprise
> > Methodology Group (http://groups.google.com/group/adf-methodology). To
> > unsubscribe send email to adf-methodolo...@googlegroups.com
>
> > All content to the ADF EMG lies under the Creative Commons Attribution 3.0
> > Unported License (http://creativecommons.org/licenses/by/3.0/). Any
> > content sourced must be attributed back to the ADF EMG with a link to the
> > Google Group (http://groups.google.com/group/adf-methodology).
>
> --
> Amir Khanof
> Senior Oracle MiddleWare Developer
>
> 09122124673
Thanks
Mashrur
Just a few thoughts:
Make sure that your application server is patched to the latest, including patches to the ADF libraries. We don’t have much experience with JDev 11g and Weblogic, but the memory use on a 10g application on OC4J was significantly reduced when we installed a fairly minor patch to the ADF libraries.
Read up on the performance tuning parameters for your Application Modules – we got a bit of a bump by fine tuning these.
Simon, while the long-time users of Oracle tools (like Forms) in my shop (including me) are using ADF BC, we have two developers who knew Hibernate, so they did the Model for their projects in JPA. Their applications simply don’t perform as well as mine. For that reason, and so that any of our developers can maintain them, the next versions of these will be switched to ADF BC.
I can't understand this equation actually. Oracle made a tool/
framework which will end up selling something expensive [web logic] to
end customer - but that tool is targeted for quick development with
less scalability option - so, who are those end customers who don't
need a scalable app but ready to pay a huge amount for infrastructure
cost [app server, hardware, etc.] ?
For example, we've recently come across a performance problem arising
from the use of the ViewRow's setters when populating programmatic
VOs(half of our applications model stack is composed of programmatic
VOs - long story). The ViewRow's setters ultimately call
setAttributeInternal() which causes events to be fired at the
ViewObject's EntityCache. So in essence, merely setting an attribute
in a row is causing a lot of code to be executed. Advice from Oracle
Support is to find a way to bypass those when possible(e.g. for our
search result screens, we don't really need to fire the EntityCache
events as the ViewObjects are serving only as data holders). This
seems to be possible using populateAttribute(a protected ViewRow
method).
I've been developing using ADF for only about a year but my conclusion
so far is that ADF is not design with performance as a primary
consideration. The cynic in me tells me that this is because oracle
wants us to buy more WebLogic licenses... :D Kidding aside, there are
other frameworks out there that can easily handle 10-100 times more
load than ADF. And if you are bold enough to venture outside of the
J2EE ecosystem, stacks like node.js can easily handle even more
(concurrent) load. Of course those kinds of frameworks have their
drawbacks in lesser ease of development(which IMO is just a euphemism
for losing the ability to hire mediocre developers and still expect
functional software).
Additionally, ADF is only half the equation. WebLogic is also a
problem by itself. I will not argue about its features. Its feature
set is massive(heck I don't even know all of the features). But
features are not free. In comparison to bare Java containers like
Tomcat, WebLogic is a giant, complicated, resource hungry
chainsaw(whereas Tomcat is *just* a good 'old handheld saw). Depending
on the situation, this may be a good or bad thing.
Even the Integrated WebLogic server is a resource hog. Start it up
without any deployed application and it still consumes a good 1GB of
memory. Combine this with Jdeveloper's 1GB and you are easily
consuming more than half of a typical developer's machine(typical in
the developing/third world at least). Put this in contrast to the
lightweight(comparatively) Eclipse/Tomcat combination and you will see
how some developers find the ADF tech stack to be a giant vat of
sticky, heavy molasses.
Chris Muir
Regards
MK
In turn I'm sure the Oracle staff are listening. However please
remember it is Christmas followed by New Year, and like you they have
family and friends to focus on as a priority.
CM.
I'd also make the point that we're not "Making everything declarative".
I don't believe anyone is telling you everything will be drag and drop
- but on the other hand it doesn't make sense for everyone in the
community to be solving the same common problems like security,
persistence etc
regards
Grant
>> the performance issue with more CPUs& RAM ?
Hi,
If we supposed that any systems with more than 400 concurrent users and more than 80 pages + 80(TF) is an Enterprise system then:
I want to get your suggestions for the installation, configuration and deployment of this enterprise system in WLS.
Have do you deployed such an Enterprise scale system with ADF(ADF Faces + ADF BC)?
How Many concurrent user do you have?
How many cluster you have and how much RAM you specified for each cluster?
What is you infrastructure (JVM + WLS version + ADF version + OS version + RAM )?
Last, why I am asking such questions? because I have deployed several enterprise systems with ADF and I see lack of performance in run-time ( I have this problem in SOA/BPM Suite11g also) I am trying to get help from a brainstorming here.
What is the reality? is ADF suitable for such an enterprise level or it is very heavy-weight for Enterprise systems?
we have done several migration from Form Builder to ADF the good-> people are satisfied with functionality, design of page and capability in page component the bad-> in the past they only has database to configure, now they have very huge RAM consumption from WLS.
one of company that I knew has 15 clusters (each cluster has around 4 GIG RAM)! to support 10000 concurrent users, is this normal?is it because ADF needs lots of resources compare to other frameworks? or it is because they do not know how to configure the system? but I am sure that they know the basic ADF performance hints (APP Pool, Connection Pool,debug=false,....).
I hope at the end of this brainstorming I found my answer to what is the best configuration for Cluster+WLS+ ADF..
To my experience, for each 150 user we need 3 gig for an Enterprise system in ADF Faces, if it is true, suppose how much RAM needed if the Facebook/Gmail/Oracle Website... was supposed to be written with ADF ;) ...
Thanks
Amir
--
--abstract--
Traditional Oracle developers have learnt to use the techniques which
get the best from the Oracle database. Java developer on the other
hand have a tendency to believe that the database is just a data store
and will take care of itself. There are options you can choose in
JDeveloper that will result in applications which your users will
curse for their poor performance, and others that will behave just
fine. This presentation looks at what happens in the database when you
choose various ADF design options and discusses ways for them to work
happily together
--abstract--
Presentation PPT:
http://www.sagecomputing.com.au/papers_presentations/JDevTune.ppsx
Penny will also be presenting this at Collaborate in 2012.
CM.
It seems there will be a real world large scale ADF application soon according to a notice just received from Oracle Support about next Gen UI.
Here is an extract:
[..]Built on Oracle’s own Application Development Framework (ADF), benefits of the redesigned UI will include:
A bit disappointed. Not the best example to backup ADF 11g.
Still don't know about the underlining layers : JPA, BC4J 10g,..?
It was a great opportunity to prove ADF 11g perf & scalability... Missed IMHO.
-Jean-Marc