Dave's thoughts on technology, with specific focus on Adobe Flex, LiveCycle, PDF, enterprise Java and related technologies. May also include rants on daily events.
Friday, December 3, 2010
Tuesday, November 30, 2010
Adobe Max 2010
I missed Adobe MAX this year. First time I've missed it since Adobe acquired Macromedia in 2005. Going through the online keynote, seems like it was great tech conference filled with gadgets and freebies.
The key of this Max conference was devices. Adobe is offering a suite of tools to help designers and develop engage in a world to target multiple media and devices; from laptops/desktops, to tablets, to phones, to TV's. All these things, one platform, to make things faster, better, cheaper.
The key isn't tools. The key is people that use the tools:
The creative that thinks about how users engage with their devices, and come up with an innovative way to interact, and to reach out and communicate.
The inquisitive that questions why things need to be done a certain way. Is there a better approach?
The methodical that architects and ensure what we are building is consistent, and sound.
The key is people that makes everything happen, and possible.
Adobe embraces this, and makes customer and user experience a primary goal of the tools, of the platform. I can't wait to see what is possible in a world of human innovation and interaction.
Dave in Vancouver
The key of this Max conference was devices. Adobe is offering a suite of tools to help designers and develop engage in a world to target multiple media and devices; from laptops/desktops, to tablets, to phones, to TV's. All these things, one platform, to make things faster, better, cheaper.
The key isn't tools. The key is people that use the tools:
The creative that thinks about how users engage with their devices, and come up with an innovative way to interact, and to reach out and communicate.
The inquisitive that questions why things need to be done a certain way. Is there a better approach?
The methodical that architects and ensure what we are building is consistent, and sound.
The key is people that makes everything happen, and possible.
Adobe embraces this, and makes customer and user experience a primary goal of the tools, of the platform. I can't wait to see what is possible in a world of human innovation and interaction.
Dave in Vancouver
Sunday, November 21, 2010
Tuesday, January 12, 2010
Pooling is your friend
Been trouble shooting performance issue on a client's server for some time now. The problem was that under heavy load, the jvm would eventually run out of heap, or the database connections ran out. I tried various JVM settings to see if i can force garbage collection to occur more frequently, but all to the same result. Our LiveCycle server wasn't able to sustain the load and dies.
Turns out that this was easily fixable by setting the pooling settings for the services inside of adminui. By setting to use pooled instances only, and a minimum and maximum pool size, we got a much more stable environment. Consequently, the garbage collection also occurred much more frequently. Under load, the LiveCycle Server didn't run out of heap space either!
To modify pooling for a service:
1. Login to admin ui
2. Click on services
3. Select application and services
4. Select service management
5. Find the process / service that you created
6. Click on pooling. update as follows
- Use pooled instance for all requests
- Initial service instance pool size set to average number of concurrent transactions expected.
- max service instance pool size set to maximum number of concurrent transactions expected
- maximum async service instance is set to 0
- invocation wait time out is set to 0.
This setting worked so far for us. I will update the blog if that's not the case.
David
Turns out that this was easily fixable by setting the pooling settings for the services inside of adminui. By setting to use pooled instances only, and a minimum and maximum pool size, we got a much more stable environment. Consequently, the garbage collection also occurred much more frequently. Under load, the LiveCycle Server didn't run out of heap space either!
To modify pooling for a service:
1. Login to admin ui
2. Click on services
3. Select application and services
4. Select service management
5. Find the process / service that you created
6. Click on pooling. update as follows
- Use pooled instance for all requests
- Initial service instance pool size set to average number of concurrent transactions expected.
- max service instance pool size set to maximum number of concurrent transactions expected
- maximum async service instance is set to 0
- invocation wait time out is set to 0.
This setting worked so far for us. I will update the blog if that's not the case.
David
Subscribe to:
Posts (Atom)