-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not currently working with 2.4.3 #1
Comments
Have you been using this and it no longer works? Or are you just trying it now? After I got it working it didn't seem to be any more performant than using the regular servlet API, so I haven't followed up. |
just tried it. if there's no real perfomance gain, no biggy :) Owen Rubel On Mon, Sep 22, 2014 at 2:52 PM, Burt Beckwith [email protected]
|
all performance gains will come with spring-boot and grails 3 :) Owen Rubel On Mon, Sep 22, 2014 at 2:52 PM, Burt Beckwith [email protected]
|
Hello, |
I only tried it with a couple of recent versions when I was developing it, and didn't see any speed improvement. So it's not worse, which is a good thing. I don't know if I did a fair test though - should compare IO-bound request handling to show that long-running requests don't affect short non-IO bound requests. But we'll be revisiting this as part of Grails 3, basing the core on Spring Boot, adding more Ratpack/Vertx/Node-style options for reactive/async, etc. But if you find anything in this plugin that's misconfigured and affecting a performance boost let me know; it'd be good to have this as a viable option. |
okay will do, thanks :) |
commented out tomcat and added this. did a 'clean-all' and then run-app and got error. same with run-war.
error is as follows
No default container found. Please install a container plugin such as 'tomcat' first.
The text was updated successfully, but these errors were encountered: