Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
Not enough memory, or too much?
Message
De
31/03/2005 12:39:52
 
 
À
31/03/2005 12:23:12
Information générale
Forum:
Visual FoxPro
Catégorie:
Codage, syntaxe et commandes
Versions des environnements
Visual FoxPro:
VFP 6 SP5
Database:
Visual FoxPro
Divers
Thread ID:
00968453
Message ID:
01000393
Vues:
19
Could there be a problem with the motherboard supporting more than 1GB?

This certainly was an issue with older MBs.

good luck


>Thanks Mike. We're talking about the same issue. If I go under 1GB, the problem disappears. That is not an option for me, though, as the performance hit of doing that is also too significant.
>
>Thanks again for your response.
>
>>I don't think I even tried SYS(3050). The specific problem our clients were facing turned out to be related to running the app on a machine with more than 1 gig of memory. They (grudgingly) switched the offending process, which only runs once a month, to a box with 1 gig of memory. That seems to have cured it.
>>
>>
>>>Did you every resolve this? I have a persistent problem with this.
>>>
>>>Sys(3050) solves it every time, but at a large cost: significant performance degradation. As you may know, optimizing a system's sys(3050) usage can have a significant performance improvement. The modification to sys(3050) required to eliminate the error moves my sys(3050) well out of the optimal performance zone - resulting in what I would guestimate to be a 50% performance hit.
>>>
>>>I will soon be re-attacking this problem, so I was wondering if you had discovered any other insights?
>>>
>>>Thanks,
>>>
>>>David
>>>
>>>
>>>
>>>>We have a client who is receiving the "Not enough memory for file map" error in some processes. (We also have about 70 clients who do not receive this error in the same processes, nor do I receive it running their data). I had thought this error happened with cursors -- the kind created with CREATE CURSOR, not the kind created with SELECT .... INTO CURSOR -- so changed the troubled processes to SELECT INTO TABLE. However, they still occur. The client is running on a dual processor system, both of them 3.2 gHz, with 2 GB of memory. Could this be one of those flaky ones where VFP malfunctions because there is too *much* memory?
>>>>
>>>>Also, is my understanding of the cause(s) of this error incorrect? Can other things cause it? I have not been able to find much information about the causes. The FoxPro help just says it happens when memory is limited and suggests adding memory. With 2 gig of memory, I don't think that's the problem....
>>>>
>>>>Thanks in advance for any assistance.
>>>>
>>>>Mike
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform