Community
Participate
Working Groups
Comment by kobylin@ca.ibm.com from bug 56183: Has the information about the range of numbers for dataChannelSize and -Xmx parameter acceptable by the profiling tooling been documented in the readme or profiling documentation ? Document the range of numbers for dataChannelSize and -Xmx parameter acceptable by the profiling tooling either in the readme or profiling documentation.
*** Bug 56183 has been marked as a duplicate of this bug. ***
I'm moving this out. Time is short and you need to focus on other issues Dave.
Will add information about setting dataChannelSize and -Xmx to the documentation.
Deferring to 3.3 i2 as it cannot be contained in i1.
Now that we have a "3.3" Version in bugzilla, updating bugzillas targeted to 3.3 or a 3.3 iteration so that their Version matches their Target. "future", "unspecified", "4.0", and "4.1" Versions will not be updated.
Changed back to original version.
Adding myself to the CC list since this has a doc hit.
Could not be contained in iteration 2. Deferring to iteration 3.
Deferring to 4.1 and reassigning to Dave to provide values for -Xmx and DataChannelSize.
Will try to contain the investigation in 4.0 i4 and document the findings in the readme.
Deferring this to 4.1 because it cannot be contained in 4.0.
Deferring this to 4.2 as agreed to my Sri.
Targetting to 4.2 i3
Dan Price no longer involved in the project.
This cannot be contained in 4.2. Documentation is frozen. Deferring to 4.3.
While this is helpful information to document it likely cannot be contained in TPTP 4.3. Work is required to investigate on each platform the suggested sizes. Note, these would be suggestions only and does not guarantee that they will work due to the many variables involved (size of application, filters specified, amount of memory available on the system, etc.). Therefore dropping the priority to P2.
After thinking about this further, I don't know how useful these suggested values would be given the many variables involved. Given that I am not aware of any other requests for this type of information, I will return this defect as "Won't Fix". If anyone disagrees with this assessment you can reopen the defect.
As of TPTP 4.6.0, TPTP is in maintenance mode and focusing on improving quality by resolving relevant enhancements/defects and increasing test coverage through test creation, automation, Build Verification Tests (BVTs), and expanded run-time execution. As part of the TPTP Bugzilla housecleaning process (see http://wiki.eclipse.org/Bugzilla_Housecleaning_Processes), this enhancement/defect is verified/closed by the Project Lead since this enhancement/defect has been resolved and unverified for more than 1 year and considered to be fixed. If this enhancement/defect is still unresolved and reproducible in the latest TPTP release (http://www.eclipse.org/tptp/home/downloads/), please re-open.
