DarenHan's Blog - All Comments

Pages tagged "cumulative"

Pages tagged "cumulative" — Sun, 21 Dec 2008 20:18:52 GMT

Pingback from Pages tagged "cumulative"

Recent URLs tagged Redundancy - Urlrecorder

Recent URLs tagged Redundancy - Urlrecorder — Thu, 04 Dec 2008 01:31:27 GMT

Pingback from Recent URLs tagged Redundancy - Urlrecorder

re: save $$ on your mobile with callback service from Hoiio

darenhan — Thu, 13 Nov 2008 17:49:00 GMT

videos:

www.youtube.com/watch

re: Pitfall of storing dataset in a session variable

cruizer — Fri, 03 Oct 2008 03:19:26 GMT

but yes, the app needs to be evaluated: does it really have to store all 60,000 rows in memory? most likely it doesn't.

re: Pitfall of storing dataset in a session variable

cruizer — Fri, 03 Oct 2008 03:18:15 GMT

@daren, well that means that RAM is the issue. storing a DataSet with 60,000 rows consumes a lot of RAM and it stressed out the server. but if the session store is in-process (within the ASP.NET handler), there is no "conversion" from a big session variable to a DataSet. the objects are stored as-is. conversion is only done if there is serialization involved, such as by having the StateServer or SQL Server as your session store.

re: Pitfall of storing dataset in a session variable

man_25 — Tue, 30 Sep 2008 14:41:30 GMT

Session is a light weight storage mechanism not intended for 60,000 rows! Also the session data must be serializable (or primitive data type) if StateServer is used.

re: Pitfall of storing dataset in a session variable

darenhan — Mon, 29 Sep 2008 16:34:26 GMT

nope, we did a test and monitor the memory usage during which we execute the code. It shoot up to 100% on the web server.

sessions are supposed to be light weighted, not fit to store so much data inside.

re: Pitfall of storing dataset in a session variable

cruizer — Fri, 26 Sep 2008 04:01:29 GMT

I think it will only be slow if the session is being stored out of process, like with an ASP.NET Session State server, or with SQL Server. But if the session storage is the built-in in-memory session store for ASP.NET, execution will be instantaneous.

Tommie

Ryder — Fri, 08 Aug 2008 04:59:31 GMT

6be0385b0640f3ef5a977671d9ec4081

<a href="njdokj.info/.../6be0385b0640f3ef5a977671d9ec4081">">njdokj.info/.../6be0385b0640f3ef5a977671d9ec4081"> njdokj.info/.../6be0385b0640f3ef5a977671d9ec4081 </a>

njdokj.info/.../6be0385b0640f3ef5a977671d9ec4081

[url]njdokj.info/.../6be0385b0640f3ef5a977671d9ec4081[url]

free stock picks

WoorytopWaift — Sun, 03 Aug 2008 05:44:37 GMT

Hi,

I have been reading this blog for some time now but never bothered to comment until today. Wanted to let you know that I am a fan and enjoy your work.

Thanks,

_________________

<a href=http://www.greencashmoney.com>Investor Newsletter</a> | <a href=http://www.greencashmoney.com>free daily stock picks</a> | <a href=http://www.greencashmoney.com>hot stock tips</a>

Hugh

Grady — Mon, 28 Jul 2008 23:49:56 GMT

bb97db72cb21aa5ee98203c1d01be7b2

<a href="njdokj.info/.../bb97db72cb21aa5ee98203c1d01be7b2">">njdokj.info/.../bb97db72cb21aa5ee98203c1d01be7b2"> njdokj.info/.../bb97db72cb21aa5ee98203c1d01be7b2 </a>

njdokj.info/.../bb97db72cb21aa5ee98203c1d01be7b2

[url]njdokj.info/.../bb97db72cb21aa5ee98203c1d01be7b2[url]

re: layman explainations behind the cryptic dot net error message

kocgeykislb — Sat, 26 Jul 2008 10:23:50 GMT

bDy05z <a href="aslgmdtsgxly.com/.../a>, [url=http://aovbyxvqdaqt.com/]aovbyxvqdaqt[/url], [link=http://exxdaqcxwekf.com/]exxdaqcxwekf[/link], http://ixsfjzzssplh.com/

flow1800

flow1800 — Mon, 21 Jul 2008 18:12:04 GMT

dskn2E gihiroef jsgiosjiogjdso igjiosdjgiodsg jwguj 94wjsdfkj gkjgl4wg dsgds

re: TestDisk Data Recovery works for most platforms

Hannes — Mon, 21 Jul 2008 07:52:08 GMT

Yep it is good, this was the only software of many that was able to repair a partition. That after some other tools actually caused a complete "loss" of all files while trying to fix boot sector.

re: Another fire-fighting case due to "cut costs"

darenhan — Wed, 09 Jul 2008 14:43:37 GMT

Adapted from Sizing and deployment guide of Crystal Enterprise 10:

"For production environments, it is recommended that the CMS database not be placed on:

1) The database server against which the reports are running

2) Any one of the Job Server or Page Server machines

3) One of the CMS machines.

The reason for this is that if the Database Server, Job Server, or Page Server is busy processing the

data for reports, the retrieval time for the CMS to query the same server will be negatively

impacted. Please refer to the Crystal Enterprise Installation guide for information on supported

CMS databases."

Currently, in our Prod server, the ce10 which is the CMS database is situated

on the same database server.

An irony which contradicts with the deployment and sizing guide of crystal enterprise 10 guide from BusinessObjects. lolz