|
Home > Archive > WebSphere Edge Server > January 2004 > Edge Server V2 Port for Opteron?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Edge Server V2 Port for Opteron?
|
|
|
| Will there be a Port for Edge Server for the AMD Opteron?
| |
|
| As long as the operating systems support that processor, then Edge will
support it.
Jeff
Mark wrote:quote:
> Will there be a Port for Edge Server for the AMD Opteron?
>
>
>
| |
|
| Currently, according to IBM's Documentation, EDGE is limited to 1.6 Gigs of
Memory. While it is a 32 bit application it should have access to 4 gigs,
but it doesn't.
Putting Edge on an OS that supports Hammer should let it access 4 gigs of
memory, but the Question is Will it?
And
porting it to the Opteron would allow it to get past 4 Gig limit.
also, where is an updated version of the Documentation for Edge PTF 2? The
documentation that came with the download did not update the information or
explain the new wording for the Activity Statics page, that is located under
http://Edgesevername/Usage/Frames
-Thanks
"JLee" <leeja@NOSPAMus.ibm.com> wrote in message
news:3EC4074A.9030000@NOSPAMus.ibm.com...quote:
> As long as the operating systems support that processor, then Edge will
> support it.
>
> Jeff
>
> Mark wrote:
>
| |
|
| I guess I should clarify what I said earlier. Edge currently supports
some 64 bit kernels and operating systems, so when the operating systems
officially support the Opteron processor then Edge would go through a
test cycle to verify Edge will run on it. Assuming that the Brand team
and management see the interest or need for supporting the processor --
so if you want it to happen, contact your IBM Marketing Rep so that
Brand knows customers want it. Let me know if you need contact information.
One complication is that Edge Server is no longer sold as a seperate
product...it has now become the Edge Components of WebSphere Application
Server v5.0 and higher. That means that support for something like this
would be decided at the WAS level and not the Edge Components level. I
doubt the Edge Server V2 package would be updated at this point for the
processor support, although I could be wrong 
Also...I've asked the support team to look into the Caching Proxy
statistics page and either point out existing documentation for any
changes (if that doc exists) or write up a "Hint & Tip" documenting the
changes and get it published on the official site. I'll try to update
here when I get a response, but you might want to keep an eye on the
support area of the official site for any updates as well.
http://www.ibm.com/software/webservers/edgeserver
Jeff
| |
|
| Thanks
-Mark
"JLee" <leeja@NOSPAMus.ibm.com> wrote in message
news:3EC53C4A.6020601@NOSPAMus.ibm.com...quote:
> I guess I should clarify what I said earlier. Edge currently supports
> some 64 bit kernels and operating systems, so when the operating systems
> officially support the Opteron processor then Edge would go through a
> test cycle to verify Edge will run on it. Assuming that the Brand team
> and management see the interest or need for supporting the processor --
> so if you want it to happen, contact your IBM Marketing Rep so that
> Brand knows customers want it. Let me know if you need contact
information.quote:
>
> One complication is that Edge Server is no longer sold as a seperate
> product...it has now become the Edge Components of WebSphere Application
> Server v5.0 and higher. That means that support for something like this
> would be decided at the WAS level and not the Edge Components level. I
> doubt the Edge Server V2 package would be updated at this point for the
> processor support, although I could be wrong
>
> Also...I've asked the support team to look into the Caching Proxy
> statistics page and either point out existing documentation for any
> changes (if that doc exists) or write up a "Hint & Tip" documenting the
> changes and get it published on the official site. I'll try to update
> here when I get a response, but you might want to keep an eye on the
> support area of the official site for any updates as well.
>
> http://www.ibm.com/software/webservers/edgeserver
>
> Jeff
>
| |
|
| No News on the Documentation?
-Mark
"JLee" <leeja@NOSPAMus.ibm.com> wrote in message
news:3EC53C4A.6020601@NOSPAMus.ibm.com...quote:
> I guess I should clarify what I said earlier. Edge currently supports
> some 64 bit kernels and operating systems, so when the operating systems
> officially support the Opteron processor then Edge would go through a
> test cycle to verify Edge will run on it. Assuming that the Brand team
> and management see the interest or need for supporting the processor --
> so if you want it to happen, contact your IBM Marketing Rep so that
> Brand knows customers want it. Let me know if you need contact
information.quote:
>
> One complication is that Edge Server is no longer sold as a seperate
> product...it has now become the Edge Components of WebSphere Application
> Server v5.0 and higher. That means that support for something like this
> would be decided at the WAS level and not the Edge Components level. I
> doubt the Edge Server V2 package would be updated at this point for the
> processor support, although I could be wrong
>
> Also...I've asked the support team to look into the Caching Proxy
> statistics page and either point out existing documentation for any
> changes (if that doc exists) or write up a "Hint & Tip" documenting the
> changes and get it published on the official site. I'll try to update
> here when I get a response, but you might want to keep an eye on the
> support area of the official site for any updates as well.
>
> http://www.ibm.com/software/webservers/edgeserver
>
> Jeff
>
| |
|
| Mark,
They're checking to see if it was written up in either of the PTF
"Updates" doc, and if not, then it will go out as a "Hint & Tip" on the
official website. Around PTF2, the connection management was improved
significantly to help performance, and that changed the statistics being
gathered. Here is a blurb about the changes -- this information will be
expanded and clarified in the official doc...
Connections
active - number of active connections (no change)
maximum - the maximum connections can be handled at the same time. It
is MaxActiveThreads * 50 with the limit of 16000. It was
MaxActiveThreads previously.
Sessions
A session has the life cycle from the acceptance of the connection till
the close.
Free session buffers are used for debugging purpose. For every
connection, a session buffer is used to keep the incoming request data.
The buffer is freed when the connection is closed and the session is
returned to the pool. But CP keeps the first 64 session buffers around
to improve the performance. Session statistical data is intended for
L2/L3 debugging problems.
Jeff
|
|
|
|
|