What should I prefer and which is faster to access, HttpContext.Application or HttpContext.Cache
I am getting huge amount of data which is frequently used and getting updated too on application start in MVC application.
I would like to know,
Which is faster to access, HttpContext.Application or HttpContext.Cache. What should I prefer.
Where does HttpContext.Cache creates memory? in RAM or in Cache Memory of Server..?
c# asp.net-mvc
add a comment |
I am getting huge amount of data which is frequently used and getting updated too on application start in MVC application.
I would like to know,
Which is faster to access, HttpContext.Application or HttpContext.Cache. What should I prefer.
Where does HttpContext.Cache creates memory? in RAM or in Cache Memory of Server..?
c# asp.net-mvc
Also, don’t confuse Cache with Session - that’s probably introducing needless concerns and questions like #2.
– user2864740
Jan 2 at 8:30
add a comment |
I am getting huge amount of data which is frequently used and getting updated too on application start in MVC application.
I would like to know,
Which is faster to access, HttpContext.Application or HttpContext.Cache. What should I prefer.
Where does HttpContext.Cache creates memory? in RAM or in Cache Memory of Server..?
c# asp.net-mvc
I am getting huge amount of data which is frequently used and getting updated too on application start in MVC application.
I would like to know,
Which is faster to access, HttpContext.Application or HttpContext.Cache. What should I prefer.
Where does HttpContext.Cache creates memory? in RAM or in Cache Memory of Server..?
c# asp.net-mvc
c# asp.net-mvc
asked Jan 2 at 7:49
Gaurav ChutkeGaurav Chutke
111
111
Also, don’t confuse Cache with Session - that’s probably introducing needless concerns and questions like #2.
– user2864740
Jan 2 at 8:30
add a comment |
Also, don’t confuse Cache with Session - that’s probably introducing needless concerns and questions like #2.
– user2864740
Jan 2 at 8:30
Also, don’t confuse Cache with Session - that’s probably introducing needless concerns and questions like #2.
– user2864740
Jan 2 at 8:30
Also, don’t confuse Cache with Session - that’s probably introducing needless concerns and questions like #2.
– user2864740
Jan 2 at 8:30
add a comment |
1 Answer
1
active
oldest
votes
Conceptually speaking..
Application is intended for data that is set ONCE per application (not necessarily at startup, maybe at point of first requirement), this exists across all user sessions/logins.
Cache is intended for data that MAY change, but can be valid for a cached period, after the period of time it will need to be re-fetched anyway.
Since you mention that your application needs to hold on to data that is being updated, this does not sound like a use for the Application object.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54002907%2fwhat-should-i-prefer-and-which-is-faster-to-access-httpcontext-application-or-h%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Conceptually speaking..
Application is intended for data that is set ONCE per application (not necessarily at startup, maybe at point of first requirement), this exists across all user sessions/logins.
Cache is intended for data that MAY change, but can be valid for a cached period, after the period of time it will need to be re-fetched anyway.
Since you mention that your application needs to hold on to data that is being updated, this does not sound like a use for the Application object.
add a comment |
Conceptually speaking..
Application is intended for data that is set ONCE per application (not necessarily at startup, maybe at point of first requirement), this exists across all user sessions/logins.
Cache is intended for data that MAY change, but can be valid for a cached period, after the period of time it will need to be re-fetched anyway.
Since you mention that your application needs to hold on to data that is being updated, this does not sound like a use for the Application object.
add a comment |
Conceptually speaking..
Application is intended for data that is set ONCE per application (not necessarily at startup, maybe at point of first requirement), this exists across all user sessions/logins.
Cache is intended for data that MAY change, but can be valid for a cached period, after the period of time it will need to be re-fetched anyway.
Since you mention that your application needs to hold on to data that is being updated, this does not sound like a use for the Application object.
Conceptually speaking..
Application is intended for data that is set ONCE per application (not necessarily at startup, maybe at point of first requirement), this exists across all user sessions/logins.
Cache is intended for data that MAY change, but can be valid for a cached period, after the period of time it will need to be re-fetched anyway.
Since you mention that your application needs to hold on to data that is being updated, this does not sound like a use for the Application object.
answered Jan 2 at 8:13
SazooCatSazooCat
11216
11216
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54002907%2fwhat-should-i-prefer-and-which-is-faster-to-access-httpcontext-application-or-h%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Also, don’t confuse Cache with Session - that’s probably introducing needless concerns and questions like #2.
– user2864740
Jan 2 at 8:30