Proj too big? Help!

[Tina]

I have an asp project that has 144 aspx/ascx pages, most with large
code-behind files. Recently my dev box has been straining and taking long
times to reneder the pages in the dev environment. After addding another
Crystal report, vs.net will no longer build the project - it just goes
away - no message no nothing. My other dev box will build it but won't run
it in debug.

I ran a vs.net repair but it still does the same thing. vs.net will still
build my other, and smaller projects just fine. Is my project too big? Is
there any information available on the practical limits of a project size?
Is memory available a factor? (I have 512). I am using vs.net Enterlprise
Architecht version 7.1.3088 with all known updates.

Any help would be appreciated.
T

 

[Alvin Bruney [MVP - ASP.NET]]

it depends on the resources that are being used in the page. you may try
user controls to reduce the page sizes

--
Regards,
Alvin Bruney - ASP.NET MVP

[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc, Amazon.com etc

 

[Tina]

Alvin, thanks for your response but that's not really a heap of help....

Is 144 page project big? the answer might be no, many project exist that
have thousands of pages. Or the answer may be that few projects are that
big and I might be on the edge. (you MVPs know the answer to that)

One thing I have noticed is that whenever the subject of a possible
limitation in a MS product comes up on these forums everyone get really
tight mouthed. It really limits the usefullness of the forums (IMHO)

T

it depends on the resources that are being used in the page. you may try
user controls to reduce the page sizes

--
Regards,
Alvin Bruney - ASP.NET MVP

[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc, Amazon.com etc

I have an asp project that has 144 aspx/ascx pages, most with large
code-behind files. Recently my dev box has been straining and taking long
times to reneder the pages in the dev environment. After addding another
Crystal report, vs.net will no longer build the project - it just goes
away - no message no nothing. My other dev box will build it but won't
run it in debug.

I ran a vs.net repair but it still does the same thing. vs.net will
still build my other, and smaller projects just fine. Is my project too
big? Is there any information available on the practical limits of a
project size? Is memory available a factor? (I have 512). I am using
vs.net Enterlprise Architecht version 7.1.3088 with all known updates.

Any help would be appreciated.
T

 

[Juan T. Llibre]

heh, heh...
Lay off the conspiracy theories... ;-)

You might want to consider increasing the RAM on your box.
512MB is woefully inadequate.

Increase RAM to at least 1GB, or more if you can afford it.
That should take care of your problem.

Alvin, thanks for your response but that's not really a heap of help....

Is 144 page project big? the answer might be no, many project exist that have thousands
of pages. Or the answer may be that few projects are that big and I might be on the
edge. (you MVPs know the answer to that)

One thing I have noticed is that whenever the subject of a possible limitation in a MS
product comes up on these forums everyone get really tight mouthed. It really limits
the usefullness of the forums (IMHO)

T

it depends on the resources that are being used in the page. you may try user controls
to reduce the page sizes

--
Regards,
Alvin Bruney - ASP.NET MVP

[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc, Amazon.com etc

I have an asp project that has 144 aspx/ascx pages, most with large code-behind files.
Recently my dev box has been straining and taking long times to reneder the pages in
the dev environment. After addding another Crystal report, vs.net will no longer build
the project - it just goes away - no message no nothing. My other dev box will build
it but won't run it in debug.

I ran a vs.net repair but it still does the same thing. vs.net will still build my
other, and smaller projects just fine. Is my project too big? Is there any
information available on the practical limits of a project size? Is memory available a
factor? (I have 512). I am using vs.net Enterlprise Architecht version 7.1.3088 with
all known updates.

Any help would be appreciated.
T

 

[Tina]

Yes, I'm going to a gig because it might fix the problem. If that doesn't
work maybe another gig might help.

hmmm... I wonder if my project is too big? Too bad there are no guidelines
or even gross heuristics. For instance maybe the compiling capablity of the
vs.net vb compiler decreases exponentially after it gets so big and no
amount of memory will suffice once a size threshold is reached. A more
scientific approach would help developers correctly size projects and
forecast hardware requirements. Scientific... yea maybe there should be a
field called "Computer Science"..

sorry, I'm frustrated
T

heh, heh...
Lay off the conspiracy theories... ;-)

You might want to consider increasing the RAM on your box.
512MB is woefully inadequate.

Increase RAM to at least 1GB, or more if you can afford it.
That should take care of your problem.

Alvin, thanks for your response but that's not really a heap of help....

Is 144 page project big? the answer might be no, many project exist that
have thousands of pages. Or the answer may be that few projects are that
big and I might be on the edge. (you MVPs know the answer to that)

One thing I have noticed is that whenever the subject of a possible
limitation in a MS product comes up on these forums everyone get really
tight mouthed. It really limits the usefullness of the forums (IMHO)

T

it depends on the resources that are being used in the page. you may try
user controls to reduce the page sizes

--
Regards,
Alvin Bruney - ASP.NET MVP

[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc, Amazon.com etc
I have an asp project that has 144 aspx/ascx pages, most with large
code-behind files. Recently my dev box has been straining and taking
long times to reneder the pages in the dev environment. After addding
another Crystal report, vs.net will no longer build the project - it
just goes away - no message no nothing. My other dev box will build it
but won't run it in debug.

I ran a vs.net repair but it still does the same thing. vs.net will
still build my other, and smaller projects just fine. Is my project
too big? Is there any information available on the practical limits of
a project size? Is memory available a factor? (I have 512). I am using
vs.net Enterlprise Architecht version 7.1.3088 with all known updates.

Any help would be appreciated.
T

 

[Juan T. Llibre]

Hi, Tina.

re:

hmmm... I wonder if my project is too big?

I doubt it.

The problem's related to the way VS.NET needs *real*
RAM available for its operations, not page-filed memory.

VS.NET *will* use the page-file, but using it slows down VS.NET.
More physical RAM is a sure-fire way to optimize VS.NET.

In the meantime, check your running applications
and shut down those you don't really need open.

There's all sorts of tweaks you can apply to improve the situation.

If you're running SQL Server on the same box,
sometimes there's contention for the use of the page file.

I found that placing the page file and the SQL temp file

sorry, I'm frustrated

Hang in there.

You'll find that once your RAM upgrade is in place,
your performance will shoot up.

512MB RAM is peanuts these days... ;-)

Yes, I'm going to a gig because it might fix the problem. If that doesn't work maybe
another gig might help.

hmmm... I wonder if my project is too big? Too bad there are no guidelines or even
gross heuristics. For instance maybe the compiling capablity of the vs.net vb compiler
decreases exponentially after it gets so big and no amount of memory will suffice once a
size threshold is reached. A more scientific approach would help developers correctly
size projects and forecast hardware requirements. Scientific... yea maybe there should
be a field called "Computer Science"..

sorry, I'm frustrated
T

heh, heh...
Lay off the conspiracy theories... ;-)

You might want to consider increasing the RAM on your box.
512MB is woefully inadequate.

Increase RAM to at least 1GB, or more if you can afford it.
That should take care of your problem.

Alvin, thanks for your response but that's not really a heap of help....

Is 144 page project big? the answer might be no, many project exist that have
thousands of pages. Or the answer may be that few projects are that big and I might
be on the edge. (you MVPs know the answer to that)

One thing I have noticed is that whenever the subject of a possible limitation in a MS
product comes up on these forums everyone get really tight mouthed. It really limits
the usefullness of the forums (IMHO)

T

"Alvin Bruney [MVP - ASP.NET]" <www.lulu.com/owc> wrote in message
it depends on the resources that are being used in the page. you may try user
controls to reduce the page sizes

--
Regards,
Alvin Bruney - ASP.NET MVP

[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc, Amazon.com etc
I have an asp project that has 144 aspx/ascx pages, most with large code-behind
files. Recently my dev box has been straining and taking long times to reneder the
pages in the dev environment. After addding another Crystal report, vs.net will no
longer build the project - it just goes away - no message no nothing. My other dev
box will build it but won't run it in debug.

I ran a vs.net repair but it still does the same thing. vs.net will still build my
other, and smaller projects just fine. Is my project too big? Is there any
information available on the practical limits of a project size? Is memory available
a factor? (I have 512). I am using vs.net Enterlprise Architecht version 7.1.3088
with all known updates.

Any help would be appreciated.
T

 

[bradley]

I don't see why the total number of pages in a project should be limited by
the amount of RAM. Of course a baseline amount of RAM is needed, but 1 GB
seems excessive. When VS.NET runs a project or builds, does it hold every
page and module in memory? Why not just hold objects in memory as needed
like the ASP.NET runtime?

Hi, Tina.

re:

hmmm... I wonder if my project is too big?

I doubt it.

The problem's related to the way VS.NET needs *real*
RAM available for its operations, not page-filed memory.

VS.NET *will* use the page-file, but using it slows down VS.NET.
More physical RAM is a sure-fire way to optimize VS.NET.

In the meantime, check your running applications
and shut down those you don't really need open.

There's all sorts of tweaks you can apply to improve the situation.

If you're running SQL Server on the same box,
sometimes there's contention for the use of the page file.

I found that placing the page file and the SQL temp file

sorry, I'm frustrated

Hang in there.

You'll find that once your RAM upgrade is in place,
your performance will shoot up.

512MB RAM is peanuts these days... ;-)

Yes, I'm going to a gig because it might fix the problem. If that doesn't work maybe
another gig might help.

hmmm... I wonder if my project is too big? Too bad there are no guidelines or even
gross heuristics. For instance maybe the compiling capablity of the vs.net vb compiler
decreases exponentially after it gets so big and no amount of memory will suffice once a
size threshold is reached. A more scientific approach would help developers correctly
size projects and forecast hardware requirements. Scientific... yea maybe there should
be a field called "Computer Science"..

sorry, I'm frustrated
T

heh, heh...
Lay off the conspiracy theories... ;-)

You might want to consider increasing the RAM on your box.
512MB is woefully inadequate.

Increase RAM to at least 1GB, or more if you can afford it.
That should take care of your problem.





Alvin, thanks for your response but that's not really a heap of help....

Is 144 page project big? the answer might be no, many project exist that have
thousands of pages. Or the answer may be that few projects are that big and I might
be on the edge. (you MVPs know the answer to that)

One thing I have noticed is that whenever the subject of a possible limitation in a MS
product comes up on these forums everyone get really tight mouthed. It really limits
the usefullness of the forums (IMHO)

T

"Alvin Bruney [MVP - ASP.NET]" <www.lulu.com/owc> wrote in message
it depends on the resources that are being used in the page. you may try user
controls to reduce the page sizes

--
Regards,
Alvin Bruney - ASP.NET MVP

[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc, Amazon.com etc
I have an asp project that has 144 aspx/ascx pages, most with large code-behind
files. Recently my dev box has been straining and taking long times to reneder the
pages in the dev environment. After addding another Crystal report, vs.net will no
longer build the project - it just goes away - no message no nothing. My other dev
box will build it but won't run it in debug.

I ran a vs.net repair but it still does the same thing. vs.net will still build my
other, and smaller projects just fine. Is my project too big? Is there any
information available on the practical limits of a project size? Is memory available
a factor? (I have 512). I am using vs.net Enterlprise Architecht version 7.1.3088
with all known updates.

Any help would be appreciated.
T

 

[Juan T. Llibre]

re:

I don't see why the total number of pages in a project
should be limited by the amount of RAM.

Every file loaded is an object, and every object consumes RAM.

Not only that, every *change* made to any object is held in memory,
so you can have the ability to undo changes to any object.

re:

When VS.NET runs a project or builds,
does it hold every page and module in memory?

There's nowhere else to hold them.

That's why you're prompted to save files when you
try to exit VS.NET without having saved your work.

The alternative would be writing directly to files,
with all the inconveniences that entails.

re:

Why not just hold objects in memory as needed
like the ASP.NET runtime?

That's a misconception.

Once an object is instantiated within ASP.NET,
it's held in memory for the lifetime of the application or session.

Since you can't have "sessions" in VS.NET, the equivalent is
to hold the objects in memory while the application is active.

I don't see why the total number of pages in a project should be limited by
the amount of RAM. Of course a baseline amount of RAM is needed, but 1 GB
seems excessive. When VS.NET runs a project or builds, does it hold every
page and module in memory? Why not just hold objects in memory as needed
like the ASP.NET runtime?

Hi, Tina.

re:

hmmm... I wonder if my project is too big?

I doubt it.

The problem's related to the way VS.NET needs *real*
RAM available for its operations, not page-filed memory.

VS.NET *will* use the page-file, but using it slows down VS.NET.
More physical RAM is a sure-fire way to optimize VS.NET.

In the meantime, check your running applications
and shut down those you don't really need open.

There's all sorts of tweaks you can apply to improve the situation.

If you're running SQL Server on the same box,
sometimes there's contention for the use of the page file.

I found that placing the page file and the SQL temp file

sorry, I'm frustrated

Hang in there.

You'll find that once your RAM upgrade is in place,
your performance will shoot up.

512MB RAM is peanuts these days... ;-)

Yes, I'm going to a gig because it might fix the problem. If that doesn't work maybe
another gig might help.

hmmm... I wonder if my project is too big? Too bad there are no guidelines or even
gross heuristics. For instance maybe the compiling capablity of the vs.net vb compiler
decreases exponentially after it gets so big and no amount of memory will suffice once a
size threshold is reached. A more scientific approach would help developers correctly
size projects and forecast hardware requirements. Scientific... yea maybe there should
be a field called "Computer Science"..

sorry, I'm frustrated
T




heh, heh...
Lay off the conspiracy theories... ;-)

You might want to consider increasing the RAM on your box.
512MB is woefully inadequate.

Increase RAM to at least 1GB, or more if you can afford it.
That should take care of your problem.





Alvin, thanks for your response but that's not really a heap of help....

Is 144 page project big? the answer might be no, many project exist that have
thousands of pages. Or the answer may be that few projects are that big and I might
be on the edge. (you MVPs know the answer to that)

One thing I have noticed is that whenever the subject of a possible limitation in a MS
product comes up on these forums everyone get really tight mouthed. It really limits
the usefullness of the forums (IMHO)

T

"Alvin Bruney [MVP - ASP.NET]" <www.lulu.com/owc> wrote in message
it depends on the resources that are being used in the page. you may try user
controls to reduce the page sizes

--
Regards,
Alvin Bruney - ASP.NET MVP

[Shameless Author Plug]
The Microsoft Office Web Components Black Book with .NET
Now available @ www.lulu.com/owc, Amazon.com etc
I have an asp project that has 144 aspx/ascx pages, most with large code-behind
files. Recently my dev box has been straining and taking long times to reneder the
pages in the dev environment. After addding another Crystal report, vs.net will no
longer build the project - it just goes away - no message no nothing. My other dev
box will build it but won't run it in debug.

I ran a vs.net repair but it still does the same thing. vs.net will still build my
other, and smaller projects just fine. Is my project too big? Is there any
information available on the practical limits of a project size? Is memory available
a factor? (I have 512). I am using vs.net Enterlprise Architecht version 7.1.3088
with all known updates.

Any help would be appreciated.
T