On Tue, Jun 28, 2016 at 12:37 PM, Rainer Jung wrote:
> Am 28.06.2016 um 18:06 schrieb therealnewo...@gmail.com:
>>
>> On Tue, Jun 28, 2016 at 11:51 AM, Rainer Jung
>> wrote:
>>>
>>> Am 28.06.2016 um 16:07 schrieb Mark Thomas:
On 28/06/2016 12:28, Mark Thomas wrote:
>
>
On Mon, Jun 27, 2016 at 5:19 PM, Mark Thomas wrote:
> On 27/06/2016 19:59, Nate Clark wrote:
>> On Mon, Jun 27, 2016 at 2:13 PM, Rainer Jung wrote:
>
>
>
>>> I wouldn't care too much about portability right now. If you can prove
>>> Mark's analysi
On Mon, Jun 27, 2016 at 2:13 PM, Rainer Jung wrote:
> Am 27.06.2016 um 18:47 schrieb Nate Clark:
>>
>> On Mon, Jun 27, 2016 at 12:17 PM, wrote:
>>>
>>> On Mon, Jun 27, 2016 at 12:04 PM, wrote:
>>>>
>>>> On Mon, Jun 27, 2016 at 11:54 A
On Mon, Jun 27, 2016 at 12:17 PM, wrote:
> On Mon, Jun 27, 2016 at 12:04 PM, wrote:
>> On Mon, Jun 27, 2016 at 11:54 AM, Rainer Jung
>> wrote:
>>> Great analysis. I was really wondering, what could make the hash map so huge
>>> and hadn't thought about the hash function as the problem.
>>>
>>
On Mon, Jun 27, 2016 at 9:11 AM, Mark Thomas wrote:
> I believe I have an explanation for what is going on that fits both the
> reported behaviour and the proposed fix.
>
> Background
> ==
>
> OpenSSL tracks a list of the most recent errors for each thread in a
> hash map keyed on the thre
On Fri, Jun 24, 2016 at 1:37 PM, Nate Clark wrote:
> On Fri, Jun 24, 2016 at 1:27 PM, Mark Thomas wrote:
>> On 24/06/2016 18:25, Mark Thomas wrote:
>>>
>>> Can you provide the settings you are using for the Executor as well please?
>
> ma
On Fri, Jun 24, 2016 at 1:27 PM, Mark Thomas wrote:
> On 24/06/2016 18:25, Mark Thomas wrote:
>>
>> Can you provide the settings you are using for the Executor as well please?
>
> And how long do the initial 5,000,000 4k requests take to process?
>
40 minutes.
-nate
-
On Thu, Jun 23, 2016 at 3:32 PM, Mark Thomas wrote:
> On 23/06/2016 20:28, Nate Clark wrote:
>>
>> If you want details about the issue I am happy to provide them but
>> just didn't wan to duplicate explaining it in a bug and in an email
>> thread.
>
> To be
Hello,
I encountered a performance issue when using the apr protocol. I
tracked it down to basically missing a piece of the integration with
openssl. I was able to fix the performance issue but it required a
change to both tomcat-native and tomcat. I was going to file a bug
with my patches but tom
