You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@jmeter.apache.org by bu...@apache.org on 2018/05/15 07:42:07 UTC
[Bug 62374] New: I suggest using Externalizable instead of
Serializable in RMI distribution test because implements Serializable took
too much network bandwidth during high throughput loading.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62374
Bug ID: 62374
Summary: I suggest using Externalizable instead of Serializable
in RMI distribution test because implements
Serializable took too much network bandwidth during
high throughput loading.
Product: JMeter
Version: 4.0
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: Main
Assignee: issues@jmeter.apache.org
Reporter: liu_xp2003@sina.com
Target Milestone: ---
I have captured network package by Wireshark and found there are too many
package path when sending a little StatisticalSampleResult data. It used up
network bandwidth during high load performance testing.
There is an article told that serialization is very easy to send more data than
is required.To solve the performance problems associated with making a class
Serializable, the serialization mechanism allows you to declare that a class is
Externalizableinstead.
Ref:
http://archive.oreilly.com/pub/a/onjava/excerpt/JavaRMI_10/index.html?page=5
--
You are receiving this mail because:
You are the assignee for the bug.
[Bug 62374] I suggest using Externalizable instead of Serializable
in RMI distribution test because implements Serializable took too much
network bandwidth during high throughput loading.
Posted by bu...@apache.org.
https://bz.apache.org/bugzilla/show_bug.cgi?id=62374
Philippe Mouawad <p....@ubik-ingenierie.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |p.mouawad@ubik-ingenierie.c
| |om
Severity|normal |enhancement
Hardware|PC |All
--
You are receiving this mail because:
You are the assignee for the bug.