Showing posts with label group. Show all posts
Showing posts with label group. Show all posts

Thursday, March 29, 2012

Performance of DataBinder.Eval

Howdy All,

I was reading an older posting about the performance hit of
DataBinder.Eval.

http://groups-beta.google.com/group...02b1685ae0f63c0

Am I correct in understanding that

<%# ((DataRowView)Container.DataIt*em)["EmployeeName"] %
would have better performance than
<%# DataBinder.Eval(Container.DataIt*em, ["EmployeeName"]) %
Does anybody have comments on this or is there a better way to set the
values of the Template Column?

thanks

dblDBL:
You are correct.

I can't give you numbers, but you ARE correct.

I will say 1 more thing however. Casting DataItem to the specific item
might be faster, but it violates your tiers and makes it harder to maintain.
Your presentation shouldn't know what TYPE of data source is being bound, it
should be implementation independent. The minute you start casting
everything, you make it a realy pain in the ass to change if you start using
collections or datasets.

Sometimes the penalty is too high to pay, but in my opinion in this case,
I'd strongly suggest you use DataBinder.Eval unless you have compelling
reasons why you shoudln't in your particular case.

Karl

--
MY ASP.Net tutorials
http://www.openmymind.net/ - New and Improved (yes, the popup is annoying)
http://www.openmymind.net/faq.aspx - unofficial newsgroup FAQ (more to
come!)

"DBLWizard" <ibflyfishin@.yahoo.com> wrote in message
news:1121106912.352713.81740@.g44g2000cwa.googlegro ups.com...
Howdy All,

I was reading an older posting about the performance hit of
DataBinder.Eval.

http://groups-beta.google.com/group...02b1685ae0f63c0

Am I correct in understanding that

<%# ((DataRowView)Container.DataIt*em)["EmployeeName"] %
would have better performance than
<%# DataBinder.Eval(Container.DataIt*em, ["EmployeeName"]) %
Does anybody have comments on this or is there a better way to set the
values of the Template Column?

thanks

dbl

Performance problem: DataSet 2 database

Hi group,
i've got a major performance problem.

I've got a dataset with 1 datatable.
This datatable has 3 columns with the following datatypes:
string 18;
datetime
decimal

There are approx 150.000 records in the datatable.
I need to save the values to the database.
Saving the records using a sp is way to slow (12 minutes!)

Does anybody have a faster way?
Ive tried:
http://www.codeproject.com/cs/database/generic_OpenXml.asp?df=100&forumid=171911&select=1344569&msg=1344569
But this didnt work due to the datetime column.

Please help me on this one!!!

TIA

VisualSanderDon't load all 150,000 records at the same time. Is there a reason you need all 150,000 records in there? Can't you do it in batches of, say, 1000?

Performance Question

I am building a portal for a college. I have offices and departments divided
into groups, and within each group there is 3 different levels of Authority:
Director
Director Delegate
Content Creator

Access to certain folder is restricted to certain group, but at the same
time it can restricted by Authority level within that group also.

Which way would be more efficient and would cause the least impact in terms
of performance:
Setting roles in web.confg as <officename>-<authority level>. there are
about 40 different offices and departments, this would mean that in the
worst-case scenario I would have 40 x 3 = 120 Roles defined in the
web.config (I was concerned that it may be too much)

Second option would be to define under each restricted directory in the
AppSettings a MinimumAuthority appSettings key, so I would read that then
concatenate it with the Group name that the user belongs to and check if the
user is in that role. That would mean that in a worst-case scenario I would
only put 40 different group names in there

which way would be more efficient

--
Abdellah Elamiri
..net Developer
Efficacy through simplicity

--
Abdellah Elamiri
..net Developer
Efficacy through simplicityIn your case, it is not a matter of efficiency because reading the options
incur a disk I/O cost. Rather you should focus on maintainability. The
webconfig file stands out here because it can be edited by most anyone with
notepad experience. In addition, changes to the roles are immediately
applied thru an application restart. Not so with the appsettings.
Appsettings are read on app startup. This is easier for non-technical people
who do not necessarily want to mess with IIS internals to apply settings.

--
Regards,
Alvin Bruney [ASP.NET MVP]
Got tidbits? Get it here...
http://tinyurl.com/27cok
"A. Elamiri" <abdellahDOTelamiriATclintonDOTedutNOSPAM> wrote in message
news:eacfoo7IEHA.3040@.TK2MSFTNGP09.phx.gbl...
>I am building a portal for a college. I have offices and departments
>divided
> into groups, and within each group there is 3 different levels of
> Authority:
> Director
> Director Delegate
> Content Creator
> Access to certain folder is restricted to certain group, but at the same
> time it can restricted by Authority level within that group also.
> Which way would be more efficient and would cause the least impact in
> terms
> of performance:
> Setting roles in web.confg as <officename>-<authority level>. there are
> about 40 different offices and departments, this would mean that in the
> worst-case scenario I would have 40 x 3 = 120 Roles defined in the
> web.config (I was concerned that it may be too much)
> Second option would be to define under each restricted directory in the
> AppSettings a MinimumAuthority appSettings key, so I would read that then
> concatenate it with the Group name that the user belongs to and check if
> the
> user is in that role. That would mean that in a worst-case scenario I
> would
> only put 40 different group names in there
> which way would be more efficient
> --
> Abdellah Elamiri
> .net Developer
> Efficacy through simplicity
> --
> Abdellah Elamiri
> .net Developer
> Efficacy through simplicity
Changes are actually done from within the Web Application which edits the
Web.Config file. No one but Administrators have access to that feature.
So it wouldn't matter if I had 120 roles stored in the web.config? I was
thinking that maybe the more the roles the more time it will take for the
Authentication logic to check whether a user belongs to a role which is
authorized

--
Abdellah Elamiri
..net Developer
Efficacy through simplicity
"Alvin Bruney [MVP]" <vapor at steaming post office> wrote in message
news:%23cFQT58IEHA.2688@.tk2msftngp13.phx.gbl...
> In your case, it is not a matter of efficiency because reading the options
> incur a disk I/O cost. Rather you should focus on maintainability. The
> webconfig file stands out here because it can be edited by most anyone
with
> notepad experience. In addition, changes to the roles are immediately
> applied thru an application restart. Not so with the appsettings.
> Appsettings are read on app startup. This is easier for non-technical
people
> who do not necessarily want to mess with IIS internals to apply settings.
> --
> Regards,
> Alvin Bruney [ASP.NET MVP]
> Got tidbits? Get it here...
> http://tinyurl.com/27cok
> "A. Elamiri" <abdellahDOTelamiriATclintonDOTedutNOSPAM> wrote in message
> news:eacfoo7IEHA.3040@.TK2MSFTNGP09.phx.gbl...
> >I am building a portal for a college. I have offices and departments
> >divided
> > into groups, and within each group there is 3 different levels of
> > Authority:
> > Director
> > Director Delegate
> > Content Creator
> > Access to certain folder is restricted to certain group, but at the same
> > time it can restricted by Authority level within that group also.
> > Which way would be more efficient and would cause the least impact in
> > terms
> > of performance:
> > Setting roles in web.confg as <officename>-<authority level>. there are
> > about 40 different offices and departments, this would mean that in the
> > worst-case scenario I would have 40 x 3 = 120 Roles defined in the
> > web.config (I was concerned that it may be too much)
> > Second option would be to define under each restricted directory in the
> > AppSettings a MinimumAuthority appSettings key, so I would read that
then
> > concatenate it with the Group name that the user belongs to and check if
> > the
> > user is in that role. That would mean that in a worst-case scenario I
> > would
> > only put 40 different group names in there
> > which way would be more efficient
> > --
> > Abdellah Elamiri
> > .net Developer
> > Efficacy through simplicity
> > --
> > Abdellah Elamiri
> > .net Developer
> > Efficacy through simplicity

Performance Question

I am building a portal for a college. I have offices and departments divided
into groups, and within each group there is 3 different levels of Authority:
Director
Director Delegate
Content Creator
Access to certain folder is restricted to certain group, but at the same
time it can restricted by Authority level within that group also.
Which way would be more efficient and would cause the least impact in terms
of performance:
Setting roles in web.confg as <officename>-<authority level>. there are
about 40 different offices and departments, this would mean that in the
worst-case scenario I would have 40 x 3 = 120 Roles defined in the
web.config (I was concerned that it may be too much)
Second option would be to define under each restricted directory in the
AppSettings a MinimumAuthority appSettings key, so I would read that then
concatenate it with the Group name that the user belongs to and check if the
user is in that role. That would mean that in a worst-case scenario I would
only put 40 different group names in there
which way would be more efficient
Abdellah Elamiri
.net Developer
Efficacy through simplicity
Abdellah Elamiri
.net Developer
Efficacy through simplicityIn your case, it is not a matter of efficiency because reading the options
incur a disk I/O cost. Rather you should focus on maintainability. The
webconfig file stands out here because it can be edited by most anyone with
notepad experience. In addition, changes to the roles are immediately
applied thru an application restart. Not so with the appsettings.
Appsettings are read on app startup. This is easier for non-technical people
who do not necessarily want to mess with IIS internals to apply settings.
Regards,
Alvin Bruney [ASP.NET MVP]
Got tidbits? Get it here...
http://tinyurl.com/27cok
"A. Elamiri" < abdellahDOTelamiriATclintonDOTedutNOSPAM
> wrote in message
news:eacfoo7IEHA.3040@.TK2MSFTNGP09.phx.gbl...
>I am building a portal for a college. I have offices and departments
>divided
> into groups, and within each group there is 3 different levels of
> Authority:
> Director
> Director Delegate
> Content Creator
> Access to certain folder is restricted to certain group, but at the same
> time it can restricted by Authority level within that group also.
> Which way would be more efficient and would cause the least impact in
> terms
> of performance:
> Setting roles in web.confg as <officename>-<authority level>. there are
> about 40 different offices and departments, this would mean that in the
> worst-case scenario I would have 40 x 3 = 120 Roles defined in the
> web.config (I was concerned that it may be too much)
> Second option would be to define under each restricted directory in the
> AppSettings a MinimumAuthority appSettings key, so I would read that then
> concatenate it with the Group name that the user belongs to and check if
> the
> user is in that role. That would mean that in a worst-case scenario I
> would
> only put 40 different group names in there
> which way would be more efficient
> --
> Abdellah Elamiri
> .net Developer
> Efficacy through simplicity
> --
> Abdellah Elamiri
> .net Developer
> Efficacy through simplicity
>
Changes are actually done from within the Web Application which edits the
Web.Config file. No one but Administrators have access to that feature.
So it wouldn't matter if I had 120 roles stored in the web.config? I was
thinking that maybe the more the roles the more time it will take for the
Authentication logic to check whether a user belongs to a role which is
authorized
Abdellah Elamiri
.net Developer
Efficacy through simplicity
"Alvin Bruney [MVP]" <vapor at steaming post office> wrote in message
news:%23cFQT58IEHA.2688@.tk2msftngp13.phx.gbl...
> In your case, it is not a matter of efficiency because reading the options
> incur a disk I/O cost. Rather you should focus on maintainability. The
> webconfig file stands out here because it can be edited by most anyone
with
> notepad experience. In addition, changes to the roles are immediately
> applied thru an application restart. Not so with the appsettings.
> Appsettings are read on app startup. This is easier for non-technical
people
> who do not necessarily want to mess with IIS internals to apply settings.
> --
> Regards,
> Alvin Bruney [ASP.NET MVP]
> Got tidbits? Get it here...
> http://tinyurl.com/27cok
> "A. Elamiri" < abdellahDOTelamiriATclintonDOTedutNOSPAM
> wrote in message
> news:eacfoo7IEHA.3040@.TK2MSFTNGP09.phx.gbl...
then
>

Wednesday, March 21, 2012

Permissions to create asp.net site

Hi.

I am creating an asp.net application using Windows 2000 Server and
VS.NET 2002. My account is part of the administrators group. I need to
share this machine with another developer. What permissions should I
give to his account in order he can successfuly create asp.net
applications, without being an administrator?

Thanks,
Robert ScheerI never run as an admin on my development box. (You should stop running as
an admin yourself.) The trickiest part to get set up is debugging. Set the
user up as a debugger user. Also, you need to run the aspnet_wp process
using the credentials of the person who is using it to get full debugging -
you can edit this directly in machine.config, and you should also
investigate the aspnet_setreg utility to encrypt these credentials so you
don't have them just sitting in plain text. I have no problems with this
configuration creating and editing asp.net applications.

--
Chris Jackson
Software Engineer
Microsoft MVP - Windows Client
Windows XP Associate Expert
--
More people read the newsgroups than read my email.
Reply to the newsgroup for a faster response.
(Control-G using Outlook Express)
--

"Robert Scheer" <rbscheer@.my-deja.com> wrote in message
news:cfd22ab6.0312011803.6ffa9ccd@.posting.google.c om...
> Hi.
> I am creating an asp.net application using Windows 2000 Server and
> VS.NET 2002. My account is part of the administrators group. I need to
> share this machine with another developer. What permissions should I
> give to his account in order he can successfuly create asp.net
> applications, without being an administrator?
> Thanks,
> Robert Scheer
Hi Chris.

What problems can I find as an administrator when developing on my .net machine?

Thanks,
Robert Scheer

"Chris Jackson" <chrisjATmvpsDOTorgNOSPAM> wrote in message news:<e03UkKPuDHA.1740@.TK2MSFTNGP12.phx.gbl>...
> I never run as an admin on my development box. (You should stop running as
> an admin yourself.) The trickiest part to get set up is debugging. Set the
> user up as a debugger user. Also, you need to run the aspnet_wp process
> using the credentials of the person who is using it to get full debugging -
> you can edit this directly in machine.config, and you should also
> investigate the aspnet_setreg utility to encrypt these credentials so you
> don't have them just sitting in plain text. I have no problems with this
> configuration creating and editing asp.net applications.
> --
> Chris Jackson
> Software Engineer
> Microsoft MVP - Windows Client
> Windows XP Associate Expert
> --
> More people read the newsgroups than read my email.
> Reply to the newsgroup for a faster response.
> (Control-G using Outlook Express)
> --
> "Robert Scheer" <rbscheer@.my-deja.com> wrote in message
> news:cfd22ab6.0312011803.6ffa9ccd@.posting.google.c om...
> > Hi.
> > I am creating an asp.net application using Windows 2000 Server and
> > VS.NET 2002. My account is part of the administrators group. I need to
> > share this machine with another developer. What permissions should I
> > give to his account in order he can successfuly create asp.net
> > applications, without being an administrator?
> > Thanks,
> > Robert Scheer