bon733
Posts: 25
|
| Posted: 08/30/2005, 10:27 PM |
|
It appears that after i press F8 to publish any changes on one page, my system becomes very slow after pressing F8. Has anyone had that experience. Any ideas?
|
 |
 |
peterr
Posts: 5971
|
| Posted: 08/30/2005, 11:48 PM |
|
This looks normal. The computer is busy generating all necessary files, searching files to publish, then publishing them. You can try using quick publishing instead (Ctrl+F8).
_________________
Peter R.
YesSoftware Forums Moderator
For product support please visit http://support.yessoftware.com |
|
|
|
bon733
Posts: 25
|
| Posted: 08/31/2005, 8:12 AM |
|
I can see that when the page is generating, but even after the program has generated I still see very high utilization.
|
|
|
|
marcwolf
Posts: 361
|
| Posted: 09/25/2005, 9:20 PM |
|
I have noticed with CCS 2.3 that it slowly takes over memory during the day.
I believe this is related to the fact that each screen opened is kept in memory until closed
Usually its a good idea to shut down CCS and reopen it again a couple of times a day. You can monitor this with the task manager and look at the memory footprint of each process.
Take care
Dave
_________________
' Coding Coding Coding
Keep Those Keyboards Coding.
Raw Code!!!!!!!
|
|
|
|
DonB
|
| Posted: 09/26/2005, 11:35 AM |
|
This isn't always a problem, though it might appear to be. Memory
management may 'cache' memory pages in anticipation of future use, yet
readily release them when they are required by other apps. Of course, CCS
*might* lock those pages exclusively, which would be a real problem.
So the apparent memory 'take over' might be nothing at all to be concerned
about. One way to test this would be to open some other large application
to see if CCS shows a decreased memory allocation.
--
DonB
http://www.gotodon.com/ccbth
"marcwolf" <marcwolf@forum.codecharge> wrote in message
news:4433777217400b@news.codecharge.com...
> I have noticed with CCS 2.3 that it slowly takes over memory during the
day.
> I believe this is related to the fact that each screen opened is kept in
memory
> until closed
>
> Usually its a good idea to shut down CCS and reopen it again a couple of
times
> a day. You can monitor this with the task manager and look at the memory
> footprint of each process.
>
> Take care
>
> Dave
> _________________
> ' Coding Coding Coding
> Keep Those Keyboards Coding.
> Raw Code!!!!!!!
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
|
xbill
Posts: 35
|
| Posted: 11/28/2005, 10:47 AM |
|
I noticed that the 3.0 betas were leaking
a lot of memory- especially with complex querys
in the Visual Query Builder.
It seems to be better with the 3.0 release.
|
|
|
|
