Which is Better/Faster isEmpty() or isBlank()?
There is method, that have some condition flow and returning empty String ''(no space) in some case. Which method is more effective/faster to use in this case: String.isEmpty() or String.isBlack()?
apex string
add a comment |
There is method, that have some condition flow and returning empty String ''(no space) in some case. Which method is more effective/faster to use in this case: String.isEmpty() or String.isBlack()?
apex string
add a comment |
There is method, that have some condition flow and returning empty String ''(no space) in some case. Which method is more effective/faster to use in this case: String.isEmpty() or String.isBlack()?
apex string
There is method, that have some condition flow and returning empty String ''(no space) in some case. Which method is more effective/faster to use in this case: String.isEmpty() or String.isBlack()?
apex string
apex string
asked Dec 11 at 15:15
voidhammer
132
132
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
String.isEmpty
is marginally faster (~0.00219ms vs ~0.00206ms, about 6%). This is such a trivially small amount that there's no reason to worry about which one you use from a performance perspective.
Practically speaking, you should generally use String.isBlank
if you expect potentially whitespace strings (e.g. from user input that may be all whitespace), and String.isEmpty
when checking fields from the database, which will never contain a string of just whitespace.
I haven't really tested it out, but would agree with such marginal difference, it mostly depends on what you want to validate -- blank vs. empty.
– Jayant Das
Dec 11 at 15:35
1
@JayantDas Yeah, a difference this small means about 0.00012ms per use, so you would need millions of uses to make a difference.
– sfdcfox
Dec 11 at 15:38
Haven't you mixed these two up?isBlank
is the one when you expect whitespace strings and not the other way around, and it must be the slower one since it needs to check characters and not just length.
– Jake Cobb
Dec 11 at 16:13
@JakeCobb That's what I get for answering before coffee. I just realized i mixed up my variables in the benchmark I was using. One sec...
– sfdcfox
Dec 11 at 16:29
add a comment |
Faster here is very broad to classify, as you will need lot of considerations to test that out. It depends on what is your use case and accordingly which method fits in best.
String.isBlank
handles any string even with white space, whereas the same is not true for String.isEmpty
. So if you expect empty string (''
) always, then using either of them should be fine.
add a comment |
String.isEmpty()
will be better. Assuming that you are not expecting strings containing just whitespace returning a true
value. If you want it to also treat strings containing whitespace as empty use String.isBlank()
The difference between the two is very slight but the docs specify what will be returned depending on input.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "459"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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%2fsalesforce.stackexchange.com%2fquestions%2f242159%2fwhich-is-better-faster-isempty-or-isblank%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
String.isEmpty
is marginally faster (~0.00219ms vs ~0.00206ms, about 6%). This is such a trivially small amount that there's no reason to worry about which one you use from a performance perspective.
Practically speaking, you should generally use String.isBlank
if you expect potentially whitespace strings (e.g. from user input that may be all whitespace), and String.isEmpty
when checking fields from the database, which will never contain a string of just whitespace.
I haven't really tested it out, but would agree with such marginal difference, it mostly depends on what you want to validate -- blank vs. empty.
– Jayant Das
Dec 11 at 15:35
1
@JayantDas Yeah, a difference this small means about 0.00012ms per use, so you would need millions of uses to make a difference.
– sfdcfox
Dec 11 at 15:38
Haven't you mixed these two up?isBlank
is the one when you expect whitespace strings and not the other way around, and it must be the slower one since it needs to check characters and not just length.
– Jake Cobb
Dec 11 at 16:13
@JakeCobb That's what I get for answering before coffee. I just realized i mixed up my variables in the benchmark I was using. One sec...
– sfdcfox
Dec 11 at 16:29
add a comment |
String.isEmpty
is marginally faster (~0.00219ms vs ~0.00206ms, about 6%). This is such a trivially small amount that there's no reason to worry about which one you use from a performance perspective.
Practically speaking, you should generally use String.isBlank
if you expect potentially whitespace strings (e.g. from user input that may be all whitespace), and String.isEmpty
when checking fields from the database, which will never contain a string of just whitespace.
I haven't really tested it out, but would agree with such marginal difference, it mostly depends on what you want to validate -- blank vs. empty.
– Jayant Das
Dec 11 at 15:35
1
@JayantDas Yeah, a difference this small means about 0.00012ms per use, so you would need millions of uses to make a difference.
– sfdcfox
Dec 11 at 15:38
Haven't you mixed these two up?isBlank
is the one when you expect whitespace strings and not the other way around, and it must be the slower one since it needs to check characters and not just length.
– Jake Cobb
Dec 11 at 16:13
@JakeCobb That's what I get for answering before coffee. I just realized i mixed up my variables in the benchmark I was using. One sec...
– sfdcfox
Dec 11 at 16:29
add a comment |
String.isEmpty
is marginally faster (~0.00219ms vs ~0.00206ms, about 6%). This is such a trivially small amount that there's no reason to worry about which one you use from a performance perspective.
Practically speaking, you should generally use String.isBlank
if you expect potentially whitespace strings (e.g. from user input that may be all whitespace), and String.isEmpty
when checking fields from the database, which will never contain a string of just whitespace.
String.isEmpty
is marginally faster (~0.00219ms vs ~0.00206ms, about 6%). This is such a trivially small amount that there's no reason to worry about which one you use from a performance perspective.
Practically speaking, you should generally use String.isBlank
if you expect potentially whitespace strings (e.g. from user input that may be all whitespace), and String.isEmpty
when checking fields from the database, which will never contain a string of just whitespace.
edited Dec 11 at 16:33
answered Dec 11 at 15:30
sfdcfox
247k11188424
247k11188424
I haven't really tested it out, but would agree with such marginal difference, it mostly depends on what you want to validate -- blank vs. empty.
– Jayant Das
Dec 11 at 15:35
1
@JayantDas Yeah, a difference this small means about 0.00012ms per use, so you would need millions of uses to make a difference.
– sfdcfox
Dec 11 at 15:38
Haven't you mixed these two up?isBlank
is the one when you expect whitespace strings and not the other way around, and it must be the slower one since it needs to check characters and not just length.
– Jake Cobb
Dec 11 at 16:13
@JakeCobb That's what I get for answering before coffee. I just realized i mixed up my variables in the benchmark I was using. One sec...
– sfdcfox
Dec 11 at 16:29
add a comment |
I haven't really tested it out, but would agree with such marginal difference, it mostly depends on what you want to validate -- blank vs. empty.
– Jayant Das
Dec 11 at 15:35
1
@JayantDas Yeah, a difference this small means about 0.00012ms per use, so you would need millions of uses to make a difference.
– sfdcfox
Dec 11 at 15:38
Haven't you mixed these two up?isBlank
is the one when you expect whitespace strings and not the other way around, and it must be the slower one since it needs to check characters and not just length.
– Jake Cobb
Dec 11 at 16:13
@JakeCobb That's what I get for answering before coffee. I just realized i mixed up my variables in the benchmark I was using. One sec...
– sfdcfox
Dec 11 at 16:29
I haven't really tested it out, but would agree with such marginal difference, it mostly depends on what you want to validate -- blank vs. empty.
– Jayant Das
Dec 11 at 15:35
I haven't really tested it out, but would agree with such marginal difference, it mostly depends on what you want to validate -- blank vs. empty.
– Jayant Das
Dec 11 at 15:35
1
1
@JayantDas Yeah, a difference this small means about 0.00012ms per use, so you would need millions of uses to make a difference.
– sfdcfox
Dec 11 at 15:38
@JayantDas Yeah, a difference this small means about 0.00012ms per use, so you would need millions of uses to make a difference.
– sfdcfox
Dec 11 at 15:38
Haven't you mixed these two up?
isBlank
is the one when you expect whitespace strings and not the other way around, and it must be the slower one since it needs to check characters and not just length.– Jake Cobb
Dec 11 at 16:13
Haven't you mixed these two up?
isBlank
is the one when you expect whitespace strings and not the other way around, and it must be the slower one since it needs to check characters and not just length.– Jake Cobb
Dec 11 at 16:13
@JakeCobb That's what I get for answering before coffee. I just realized i mixed up my variables in the benchmark I was using. One sec...
– sfdcfox
Dec 11 at 16:29
@JakeCobb That's what I get for answering before coffee. I just realized i mixed up my variables in the benchmark I was using. One sec...
– sfdcfox
Dec 11 at 16:29
add a comment |
Faster here is very broad to classify, as you will need lot of considerations to test that out. It depends on what is your use case and accordingly which method fits in best.
String.isBlank
handles any string even with white space, whereas the same is not true for String.isEmpty
. So if you expect empty string (''
) always, then using either of them should be fine.
add a comment |
Faster here is very broad to classify, as you will need lot of considerations to test that out. It depends on what is your use case and accordingly which method fits in best.
String.isBlank
handles any string even with white space, whereas the same is not true for String.isEmpty
. So if you expect empty string (''
) always, then using either of them should be fine.
add a comment |
Faster here is very broad to classify, as you will need lot of considerations to test that out. It depends on what is your use case and accordingly which method fits in best.
String.isBlank
handles any string even with white space, whereas the same is not true for String.isEmpty
. So if you expect empty string (''
) always, then using either of them should be fine.
Faster here is very broad to classify, as you will need lot of considerations to test that out. It depends on what is your use case and accordingly which method fits in best.
String.isBlank
handles any string even with white space, whereas the same is not true for String.isEmpty
. So if you expect empty string (''
) always, then using either of them should be fine.
answered Dec 11 at 15:34
Jayant Das
12.1k2623
12.1k2623
add a comment |
add a comment |
String.isEmpty()
will be better. Assuming that you are not expecting strings containing just whitespace returning a true
value. If you want it to also treat strings containing whitespace as empty use String.isBlank()
The difference between the two is very slight but the docs specify what will be returned depending on input.
add a comment |
String.isEmpty()
will be better. Assuming that you are not expecting strings containing just whitespace returning a true
value. If you want it to also treat strings containing whitespace as empty use String.isBlank()
The difference between the two is very slight but the docs specify what will be returned depending on input.
add a comment |
String.isEmpty()
will be better. Assuming that you are not expecting strings containing just whitespace returning a true
value. If you want it to also treat strings containing whitespace as empty use String.isBlank()
The difference between the two is very slight but the docs specify what will be returned depending on input.
String.isEmpty()
will be better. Assuming that you are not expecting strings containing just whitespace returning a true
value. If you want it to also treat strings containing whitespace as empty use String.isBlank()
The difference between the two is very slight but the docs specify what will be returned depending on input.
answered Dec 11 at 15:27
Jonathon Chambers
1889
1889
add a comment |
add a comment |
Thanks for contributing an answer to Salesforce Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2fsalesforce.stackexchange.com%2fquestions%2f242159%2fwhich-is-better-faster-isempty-or-isblank%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