Dear Mr Shuklendu,
Really nice to know you are tuning your web pages for enhancing its performance.
Pl let us know once your web site has been modified with' User id and password ' instead of 'Mobile number and password'. For the job details, what is existing at present is fine with us.
For testing purpose, we will require a test e-mail id & password.
Thanks & Regards
Revathi
Really nice to know you are tuning your web pages for enhancing its performance.
Pl let us know once your web site has been modified with' User id and password ' instead of 'Mobile number and password'. For the job details, what is existing at present is fine with us.
For testing purpose, we will require a test e-mail id & password.
Thanks & Regards
Revathi
On Fri, Nov 25, 2011 at 11:24 PM, <shuklendu.baji@sentientsystems.net>
wrote:
Hello Revathi,
As you know, we have been tuning web site pages to
improve the server response to the widget. We have made changes to all 3 pages,
Alert, Detail & Apply. We can now observe a significant improvement in
Alert & Detail pages and a small improvement in Apply page.
We need to make further improvements in Alert &
Apply pages. Our review of these pages suggest that major performance hit is
coming due to authenticating the jobseeker from his/her mobile no. The mobile
no. field in the server database is a free text field (it was never designed
for login purposes). This field has totally unstructered data, as shown in
examples below,
+91 9800220348
9821762252, 9920511872
602-234-6782
88002 56259
Because of this, mobile no has to be quried using LIKE
operator instead of = operator. We cannot use index on this field. Even free
text index is not working due to use of spaces, dashes, etc.
Also, the mobile no stored in a different table and
the password is in another table. We have to join the 2 tables to search on
Mobile No+Password combination.
Therefore, we propose that we use User ID (usually
e-mail id) and Password instead of Mobile No & Password. User id and
password are stored in the same table. Both fields can be indexed for fast
query. This should improve the performance markedly.
Thus, we propose following interface between server
and widget.
Alert
Data: 2 textboxes, for User ID & Password
Detail
Data: 2 textboxes, for User ID & Job ID
Aply
Data: 2 textboxes, for User ID & Job ID
If your team is ok with this plan, we will go ahead
and make these pages. We will inform when these pages are ready, so that you
can make necessary changes to the widget.
About changing the display of job detail page as
suggested by your UI designer, how do you want the data to come from server.Is
a HTML table ok? Or do you require a line separator character at the place the
output will be broken into another line? If seperator has to be used, we need
to decide on a character that will not appear in job details (say | or \).
Let us know about these 2 points (1. using userd
instead of mobile no, 2. Job detail display).
Thanks
Shuklendu
No comments:
Post a Comment