the maximum number of LSCS transactions per second?

sahu

How can we know the maximum number of LSCS transactions per second ?

Platform windows2008, TS and LS 7.3.1

Find more posts tagged with

Comments

sheikh1

Do you mean deploying from sitepublisher to your runtime?

Rick Poulin

How can we know the maximum number of LSCS transactions per second ?

If you're asking about how much throughput your existing LSCS server is licensed for, there's no way to tell because it's not stored anywhere (not even in the LSCS.lic).

If you're asking about how much throughput your server is currently handling, you can turn on profiling via the "profilingOn" and "statsLoggingPeriod" properties in lscs-conf.properties, and then using the /lscs/v1/admin/diags query. Obviously you probably shouldn't turn this on in production.

If you're asking what value you should put in the "maximum transactions per sec" field when requesting an LSCS license, there's no easy way to estimate that, but it should have already been established when you bought the product. Just put in the number that was agreed in your sales contract.

Migrateduser

If you're asking what value you should put in the "maximum transactions per sec" field when requesting an LSCS license, there's no easy way to estimate that, but it should have already been established when you bought the product. Just put in the number that was agreed in your sales contract.

In my case I need to estimate the "transactions per second" to allow HP to make an offer for new LiveSite licenses.

Situation:
Intranet
avg 60.000 page views per month (Peek, workday mornings when people start op there browser with intranet as default homepage)
expected avg. number of components per page 5

What else do I need to make an estimate?

Rick Poulin

avg 60.000 page views per month
expected avg. number of components per page 5

These stats don't matter, as they need max queries per second. If you have an existing production solution, you can just turn on throughput monitoring in LSCS and report what numbers you get in your peak time. Otherwise, use web analytics to take a look at your peak time for throughput information, and do the math to get a page views per second averaged out over the hour or two. Then, adjust that number for page and component caching, which is going to be a bit of a guess, but should make the number smaller.

Rick Poulin

Another thing came to mind last night (because I spend my evenings thinking about devnet posts).. last time I had this conversation with HP/A/I, queries of the type "get me the metadata for the current page" didn't count towards this limit. By "queries" they mean actual search queries, like "give me the 5 most recent DCRs of type X". You should clarify whether your sales rep is speaking that language too, as your number of queries counted against the limit will drop drastically when that's the case.

nipper

Another thing came to mind last night (because I spend my evenings thinking about devnet posts).. last time I had this conversation with HP/A/I, queries of the type "get me the metadata for the current page" didn't count towards this limit. By "queries" they mean actual search queries, like "give me the 5 most recent DCRs of type X". You should clarify whether your sales rep is speaking that language too, as your number of queries counted against the limit will drop drastically when that's the case.

I had a discussion with one of the sales critters about this exact topic last week. They are moving away from transaction counts and to page loads for that exact reason.

Migrateduser

I had a discussion with one of the sales critters about this exact topic last week. They are moving away from transaction counts and to page loads for that exact reason.

Although "my" sales rep requests info on the TPS, Iwov Support advices to analyze the access logs and calculate back to pageviews per second.

I have asked HP Sales to check and report back on what the correct policy is.

As soon as (if) I get feedback I'll post it

Migrateduser

I have asked HP Sales to check and report back on what the correct policy is.

The sales rep. requested the number of page views per month mentioning it would be sufficient to determine what license is required.
It was not mentioned if this will now be the official policy to determine the license type for Livesite.

hearder.rptdesign