Elfo

a

a

a

1 hour ago, xdem said:

kala entaksi eisai terma ilithios, de milame gia lefta stin ksaderfi edw, o xazos pou rwtaei tha plirwthei gia douleia

Άστον δεν. Δεν.

a

a

a

Γράψε Kotlin και άσε την Java

a

1 hour ago, Nightw0lf said:

μόνο εγώ είδα ότι στο default δεν έχει καν break;

Είναι redundant

Όλοι οι πλούσιοι έχουν ανάγκη να flexάρουν στο MxC. Γελάω

22 minutes ago, Auleon said:

o @Kara` akoma na ginei promote? mexri pou tha ftasoun ta plokamia tou forum?

Τον έφαγε το κύκλωμα

a

a

a

Just now, Nightw0lf said:

You can leave a comment in the forum or in assembla commit this topic is only for updates, and news, you should know that.

I'd say the mxc topic is a fairly good place to leave comments for such things as well. Highly doubt anybody would log in 2 other platforms for some feedback.

a

a

a

a

a

a

a

4 minutes ago, Kara` said:

We said the same thing using different words. Seem like hikari is the way to go in terms of management of connection but speaking of speed the difference is small i don't see why you wrote "if thats what you understood". I didn't say it's trash i said back when i tried it, it had many problems. (in 2016 or so i can't remember exactly) and i didn't notice any difference. Maybe i didn't knew for the con handling performance and i just tried to compare speed.

No we did not say the same thing. It is faster. Way faster. You need scale to see the difference. An l2 server is not scale. It merely scratches the surface because it's fairly conservative with it's sql connections. You also won't see a noticeable (or any) difference if you remove the CP all together and you add proper connector configuration.

The fact that you had problems doesn't mean that it doesn't work. You also can't understand Go but that doesn't make it a bad programming language. You clearly had no clue in configuring it. Sometimes, it's better to say "I don't know" instead of spitting false statements.

5 minutes ago, Kara` said:

So basically the inner-configuration is well structured in Hikari and it doesn't create a flood. In terms of speed there is no huge difference to switch right away as i can see.

If that's what you understood, I can't help you. At this point it is known that Hikari is the way to go in terms of connection management and performance with Tomcat JDBC being a close second. c3p0 is considered legacy software, it's not really maintained actively anymore and everybody who's doing something serious in the industry has moved away from it.

On the other hand l2j is not considered something serious so c3p0 is good enough, because nobody really knows much about data in here.