Skip to main content

 


Anybody can tell what the sizing criteria are for K2.net servers or how I can do my calculations to know if I need another server for K2.net.


How many transactions can K2.net handle per CPU? How many instances can it process?


I do have a single k2.net 2003 installation, even I have small number of processes, but I'm afraid this would be affected by number of instances of those processes.


Can anyone help me on this?


Thanks,


Jallad

Hi Jallad,


 These 2 threads might be useful.


http://k2underground.com/forums/thread/8075.aspx


http://k2underground.com/forums/thread/7696.aspx


All in all, without understanding the various factors in the environment, usage patterns and process design, I would say everything would be a guesstimate.  Typically planning for 250 concurrent users per CPU is a rule of the thumb but various factors will affect this.  e.g. Good/Bad process design, user usage patterns, transaction load, hardware optimization, SQL optimization, etc.

It's good to isolate SQL Server to its own box with lots of memory, log does build up quickly which affects performance on search and history drill down (and report).

Hi Johnny,


This is vasubabu.I am from India.I am doing Sharepoint developer & k2.net.How is in singapore these Sharepoint and k2.net(.net)


Regards,


Vasubabu M.

Hi Vasubabu,


 Are you referring to the job market in Singapore?  I would say It's pretty good here.  There's quite a lot of customers looking at implementing MOSS and K2.

Hi,


How r u? My brother is doing Project Manager in singapore(Rafils).I need to came singapore.How is Sharepoint & K2.net?Can you send  Ezlink group Link.


Thanks,


Vasubabu M

So in the end


1. 250 user per CPU


2. Stand alone SQL Server with lots of memory

Reply


View our Community Site Map

Nintex Community Sitemap
Terms & ConditionsCookie settings